Observatory MCP server
{
"mcpServers": {
"warmthengine-observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp"
}
}
}{
"mcpServers": {
"warmthengine-observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp"
}
}
}{
"mcpServers": {
"warmthengine-observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp"
}
}
}{
"servers": {
"warmthengine-observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp"
}
}
}{
"mcpServers": {
"warmthengine-observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.21.0
What it does
The Warmth Engine Observatory tracks AI infrastructure coordination dynamics across geopolitical blocs through a verified event database, coordination connections, and capability profiles of 20 state actors. It exposes this data via MCP tools for AI systems to query verified coordination intelligence, including events, relationships, infrastructure threads, and sovereign capability assessments.
- Query verified AI infrastructure coordination events filtered by tier, domain, geography, and environmental impact to understand geopolitical AI coordination patterns.
- Trace infrastructure threads to see where the same AI chips, accelerators, energy sources, or fabrication facilities appear across multiple coordination events.
- Assess 20 state actors' sovereign control across the AI infrastructure stack using a 7-dimension framework and track which actors are approaching designation status changes.
Tools this server exposes
| Tool | Does |
|---|---|
| search_events | Search verified AI infrastructure coordination events by keywords, filters, and classifications. |
| get_event | Retrieve a specific verified coordination event with full details. |
| get_connections | Retrieve Coordination Connections (documented relationships between events). |
| get_connection_by_id | Retrieve a specific Coordination Connection by identifier. |
| get_actors | Retrieve information about tracked state actors and geopolitical blocs. |
| get_coverage_stats | Get statistical summaries of event coverage by tier, domain, and geography. |
| get_methodology | Retrieve documentation of WEO verification and classification methodology. |
| get_topology | Retrieve the coordination topology backbone mapping directional relationships across events. |
| traverse_coordination | Traverse coordination lineage to follow Policy Cascades, Funding Flows, and other directional patterns. |
| get_capability_signatures | Retrieve capability profiles and sovereignty assessment signatures for state actors. |
| get_capability_links | Retrieve links between capability assessments and supporting events. |
| get_threads | Query infrastructure threads documenting where the same AI infrastructure asset appears across verified events. |
| get_event_stack | Retrieve layered context for an event across coordination, material, and capability dimensions. |
| query_scp | Query the Sovereign Capability Profile framework for state actors' AI infrastructure control assessments. |
| get_blocs | Retrieve definitions and membership of tracked geopolitical blocs. |
| get_contribution | Retrieve contribution or attribution information for events and connections. |
| get_metrics | Retrieve quantitative metrics about the coordination intelligence dataset. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.