About Warmth Engine Observatory
Warmth Engine Observatory (WEO) tracks verified AI infrastructure coordination events and relationships across geopolitical blocs. Researchers and analysts can query its evidence-backed event data, coordination patterns, and sovereign capability assessments through its read-only MCP tools.
Key features
- 01Search verified coordination events
- 02Explore event connections and topology
- 03Query sovereign capability profiles
- 04Inspect infrastructure threads
- 05Retrieve methodology and commitment data
Use cases
- 01Research cross-bloc AI infrastructure coordination
- 02Trace relationships across documented events
- 03Compare sovereign control of AI infrastructure
- 04Review verified compute commitments
MCP support
The MCP server provides 18 read-only tools for querying verified events, connections, actors, topology, capability profiles, infrastructure threads, methodology, and compute commitments. Access is token-authenticated.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://warmthengine.com/mcpclaude mcp add --transport http com-warmthengine-observatory https://warmthengine.com/mcp{"mcpServers":{"com-warmthengine-observatory":{"type":"http","url":"https://warmthengine.com/mcp"}}}Open in Cursor{"servers":{"com-warmthengine-observatory":{"type":"http","url":"https://warmthengine.com/mcp"}}}Open in VS Code{"mcpServers":{"com-warmthengine-observatory":{"type":"http","url":"https://warmthengine.com/mcp"}}}{"mcpServers":{"com-warmthengine-observatory":{"serverUrl":"https://warmthengine.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://warmthengine.com/mcpAuth requiredTools
17| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | No | Keyword search across event name and description |
| bloc | string | No | Filter by bloc: Western, Eastern, Western-Led, Eastern-Led, Cross-Bloc |
| tier | integer | No | Filter by tier: 1, 2, or 3 |
| domain | string | No | Filter by domain: Technology, Energy/Infrastructure, Security, Trade |
| type | string | No | Filter by event type: Policy, Infrastructure, Corporate, Coordination |
| industry | string | No | Filter by primary industry tag |
| limit | integer | No | Number of results (default 20, max 50) |
Details
From the project READMEWarmth Engine Observatory (WEO)
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
- Compute Commitment Register — Verified commitments of computing capacity to societal challenges, one record per publicly documented instrument, assigned to the Challenge List Reference; published as dated observations at
/commitments/and via/api/commitments - MCP Integration — Model Context Protocol server at
warmthengine.com/mcpexposing eighteen 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, get_commitments)
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/*andwarmthengine.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 six publications, all available on Zenodo with DOI registration:
Core Documentation
| Publication | DOI |
|---|---|
| WEO Methodology Manual — Operational specification covering event verification, significance assessment, tier classification, domain classification, industry tagging, environmental nexus tagging, and Coordination Connection methodology | 10.5281/zenodo.18427565 |
| WEO Methodology Rationale — Companion document providing empirical derivation, theoretical grounding, and calibration justification for all methodology components | 10.5281/zenodo.18427582 |
Methodology Extensions
| Publication | DOI |
|---|---|
| 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 tiers | 10.5281/zenodo.18427586 |
| WEO Contribution Architecture — Account of the platform's methodological contributions and their derivation | 10.5281/zenodo.21495917 |
| The Compute Commitment Register — Methodology Working Note — Method, Challenge List Reference, and pilot observations for the register of computing capacity committed to societal challenges | 10.5281/zenodo.22785950 |
Self-Hosted Documentation
The V1.5 Manual and Rationale are self-hosted as navigable HTML with granular section anchoring:
- Manual:
warmthengine.com/research/methodology/manual/(490 section anchors) - Rationale:
warmthengine.com/research/methodology/rationale/(193 section anchors) - Compute Commitment Register — Methodology Working Note:
warmthengine.com/research/compute-commitment-register/(66 section anchors) - Errata & Corrigenda:
warmthengine.com/research/methodology/errata/— V1.5 errata and corrigenda (expression corrections and substantive corrections to reported findings, with machine-readableerrata.json)
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
├── events-free.json # Static fallback (free-tier event data)
├── commitments/
│ └── index.html # Compute Commitment Register page
├── profiles/
│ └── index.html # Sovereign Capability Profiles page (generated)
├── scripts/
│ └── generate_profiles.py # Profiles page generator (actors JSON → HTML)
├── 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
- Website: warmthengine.com
- Email: [email protected]
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.