Warmth Engine Observatory (WEO)

MCP serverDev tools

Once added, your AI can explain how AI infrastructure efforts are coordinated across geopolitical blocs. Observatory is a dev-tools integration that provides this coordination intelligence, so you can ask your AI about these dynamics whenever you need them.

Available today. Use it from your connected AI after setup.

Add Observatory to your AI, then ask it about AI infrastructure coordination across geopolitical blocs. You can also browse the project on GitHub at github.com/warmthengine/warmth-engine-observatory.

Then ask your AI: use Warmth Engine Observatory (WEO) to search events

What your AI can do with it

  • Track AI infrastructure coordination dynamics across geopolitical blocs
  • Get coordination intelligence on AI infrastructure
  • Look up how coordination dynamics vary across geopolitical blocs
  • Answer questions about AI infrastructure coordination

From the project's README

As published by warmthengine/warmth-engine-observatory in README.md.

AI Infrastructure Coordination Dynamics


Overview

The Warmth Engine Observatory tracks AI infrastructure coordination dynamics across geopolitical blocs through verified events and mapped Coordination Connections.

Scope: WEO tracks systemic AI infrastructure coordination — observable coordination dynamics between major power centres (currently nation-states and geopolitical blocs). This differs from operational AI infrastructure management, which addresses how organisations run their own AI systems.

Live Platform: www.warmthengine.com


Platform Components

  • Event Database — Verified AI infrastructure coordination events classified by tier (Cross-Bloc, Between-Bloc, Intra-Bloc) and domain (Energy/Infrastructure, Security, Technology, Trade), tagged by industry sector (11-category GICS-anchored taxonomy) and assessed for environmental intersections via Environmental Nexus Tags (5-type ENT taxonomy with Warmth Engine Ratio)
  • Coordination Connections — Documented relationships between events revealing structural patterns across the database (Policy Cascade, Joint Issuance, Funding Flow, Regulatory Enablement, Response, Framework Family, Parallel Policy)
  • Interactive Map — Geographic visualisation of global AI infrastructure deployment
  • Interactive Atlas — Network, timeline, and connectedness analytical surface for exploring coordination topology and event relationships via Cytoscape.js
  • Evidence-Based Verification — Every event verified through primary and corroborating sources with gold standard evidentiary requirements
  • Sovereign Capability Profiles — 7-dimension framework assessing 20 state actors' sovereign control across the AI infrastructure stack, with four designation levels (PAA, AIK, ACS, Participant); includes qualification headlines, constraint summaries, sourced evidence, and severance analysis
  • Profiles Page — Standalone /profiles/ page rendering the full SCP panel with dimension filtering, actor detail expansion, and Dimension Watch table
  • Dimension Watch — Forward-looking monitoring table identifying actors approaching a designation status change at the next assessment cycle, with trigger conditions and timeline estimates
  • Infrastructure Threads — Factual cross-event links documenting where the same AI infrastructure asset (chip or accelerator, energy source, or fabrication facility) appears across multiple verified events, with four link types (fabricated_at, deploys, trains_on, powered_by); toggleable overlay on the Atlas and queryable via get_threads
  • Guided Journeys — Operator-curated analytical pathways across three substrates on the Atlas: coordination (directional coordination lineage), hardware (infrastructure thread links), and all layers (fusion traversal spanning coordination, material, and capability layers)
  • Coordination Topology — Parent-child coordination backbone mapping directional relationships (Policy Cascade, Funding Flow, Regulatory Enablement, Response) across the event corpus, powering the Atlas network view
  • MCP Integration — Model Context Protocol server at warmthengine.com/mcp exposing seventeen programmatic tools for AI systems to query verified Coordination Intelligence (search_events, get_event, get_connections, get_connection_by_id, get_actors, get_coverage_stats, get_methodology, get_topology, traverse_coordination, get_capability_signatures, get_capability_links, get_threads, get_event_stack, query_scp, get_blocs, get_contribution, get_metrics)

Architecture

The platform uses a decoupled architecture: HTML files serve as lightweight UI shells that fetch data dynamically from the WEO API (Cloudflare Worker + KV).

  • Data source: Cloudflare KV via WEO API (warmthengine.com/api/)
  • MCP endpoint: warmthengine.com/mcp (Model Context Protocol for AI agent access)
  • Authentication: Token-based (?token=weo_xxx) for API and MCP consumers; password header for website
  • Fallback: Static JSON file for API downtime resilience
  • Hosting: GitHub Pages with custom domain
  • Routes: Managed via wrangler.toml (warmthengine.com/api/* and warmthengine.com/mcp*)

Data updates flow through the API — no HTML changes required for new events or connections.


Methodology Documentation

The WEO methodology is documented across four publications, all available on Zenodo with DOI registration:

Core Documentation

PublicationDOI
WEO Methodology Manual — Operational specification covering event verification, significance assessment, tier classification, domain classification, industry tagging, environmental nexus tagging, and Coordination Connection methodology10.5281/zenodo.18427565
WEO Methodology Rationale — Companion document providing empirical derivation, theoretical grounding, and calibration justification for all methodology components10.5281/zenodo.18427582

Methodology Extensions

PublicationDOI
Towards Coordination Science: A Framework for Measuring Geopolitical Coordination Dynamics Through Event Relationship Patterns — Coordination Connection metrics and theoretical foundations (Layer 2 framework)10.5281/zenodo.18427584
Tier-Crossing Dynamics in Coordination Networks: A Methodology Extension for Cross-Level Connection Analysis — Analytical framework for examining Coordination Connections across different tiers10.5281/zenodo.18427586

Self-Hosted Documentation

The V1.5 Manual and Rationale are self-hosted as navigable HTML with granular section anchoring:

A semantic dictionary (data/weo-methodology-map.json) maps 185 WEO-specific terms to their methodology section anchors, serving both human tooltip navigation and the MCP get_methodology tool.


Repository Structure

warmth-engine-observatory/
├── index.html                  # Main platform (interactive map)
├── atlas.html                  # Interactive atlas (network/timeline/connectedness)
├── events.html                 # Events database
├── methodology.html            # Methodology overview
├── blocs.html                  # Bloc analysis
├── research.html               # Research publications
├── about.html                  # About WEO
├── support.html                # Supporter access
├── legal.html                  # Legal information
├── 404.html                    # Custom error page
├── profiles/
│   └── index.html                  # Sovereign Capability Profiles page (generated)
├── scripts/
│   └── generate_profiles.py        # Profiles page generator (actors JSON → HTML)
├── data/
│   ├── events-free.json            # Static fallback (free-tier event data)
│   └── weo-methodology-map.json    # 185 term-to-anchor semantic mappings
├── research/
│   └── methodology/
│       ├── errata/                 # V1.5 Errata Register (HTML + errata.json)
│       ├── manual/                 # Self-hosted V1.5 Manual (HTML + PDF)
│       ├── materials-register/     # AI-Critical Materials Register (HTML)
│       └── rationale/              # Self-hosted V1.5 Rationale (HTML + PDF)
├── sitemap.xml                 # XML sitemap for search engines
├── robots.txt                  # Crawler directives
├── og-image.png                # Open Graph social preview image
├── favicon_48x48.png           # Browser tab icon (48px)
├── favicon_32x32.png           # Browser tab icon (32px)
├── favicon_16x16.png           # Browser tab icon (16px)
├── CNAME                       # Custom domain configuration
├── LICENSE.md                  # Licence information
└── README.md                   # This file

Citation

If using this platform or its methodology in research, please cite:

Warmth Engine Observatory (WEO)
Warmth Engine, 2026
https://www.warmthengine.com
Licensed under CC BY 4.0

Contact


Acknowledgements

This platform uses the following open-source libraries and typefaces:

  • Leaflet (BSD-2-Clause) — Interactive map functionality
  • Leaflet.markercluster (MIT) — Map marker clustering
  • Geist (SIL Open Font Licence) — Primary typeface
  • Geist Mono (SIL Open Font Licence) — Monospace typeface
  • Cytoscape.js (MIT) — Network graph visualisation (Atlas)

Licence

Methodology documentation is licensed under Creative Commons Attribution 4.0 International.

The platform, event database, and data products are proprietary.

See LICENSE.md for full details.

Tools it offers (17)

What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • search_events
  • get_event
  • get_connections
  • get_actors
  • get_coverage_stats
  • get_methodology
  • get_connection_by_id
  • get_topology
  • traverse_coordination
  • get_capability_signatures
  • get_capability_links
  • get_threads
  • get_event_stack
  • query_scp
  • get_blocs
  • get_contribution
  • get_metrics

Signals

GitHub stars
1
Last commit
Sep 2026
Advanced
Delivery
observatory MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
com-warmthengine-observatory
Source
github.com/warmthengine/warmth-engine-observatory
Hosted endpoint
https://warmthengine.com/mcp