Skip to content
External endpointresponds

Warmth Engine Observatory

AI infrastructure coordination: events, connections, profiles, topology, capability, threads, blocs

Endpoint URL
https://warmthengine.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
357 ms
Response record
4 of 4 rounds
Transport
sse
Source
mcp_registry
Registry name
com.warmthengine/observatory

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Warmth Engine Observatory
Version
1.18.7
Capability keys
tools, prompts, resources
Tool names
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
Instructions excerpt

The Warmth Engine Observatory tracks AI infrastructure coordination dynamics across geopolitical blocs. This server provides 17 read-only tools over a corpus of verified events, typed Coordination Connections, Sovereign Capability Profiles, coordination topology, Infrastructure Threads, and methodology lookup. DATA TIERS Free (unauthenticated): the full shape of the corpus — every event's classification, description, investment picture, and Environmental Nexus Tags; every Coordination Connection's structural record; the complete coordination topology with traversal; capability signatures and event-to-dimension capability links; every actor's designation and seven-dimension heatmap; Infrastructure Threads; the Bloc Membership Register; and methodology resolution. Analyst (authenticated): adds the evidence layer — source URLs with archival snapshots, tier rationales, bloc analyses, significance framework assessments (Basel-5/Keohane/PISA-5/Route-Based), full SCP dimensional analyse

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 327ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 591ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 223ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 357ms