# Warmth Engine Observatory MCP server

AI infrastructure coordination intelligence: events, connections, sovereign profiles, methodology.

## Links
- Registry page: https://www.getdrio.com/mcp/com-warmthengine-observatory
- Repository: https://github.com/warmthengine/warmth-engine-observatory

## Install
- Endpoint: https://warmthengine.com/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://warmthengine.com/mcp
- Header: Authorization

## Tools
- search_events - Search and filter the WEO event corpus by keyword or classification (bloc, tier, domain, event type, primary industry tag); returns the matching events with their metadata, capped by `limit` (default 20, max 50). Use to discover or shortlist events; for a single event's complete record, use `get_event`. Free tier returns the classification facts with the deeper assessment and evidence withheld on non-sample events; full tier — and sample events on either tier — return every field. Endpoint: https://warmthengine.com/mcp
- get_event - Retrieve one event by ID — classification, assessment, sources, industry tags, Environmental Nexus Tags (ENTs), bloc analysis, and tier rationale. Use when you already hold an event ID; to find IDs, use `search_events`. Pass `event_id` as the zero-padded string (e.g. "06", "141"). Free tier returns the complete record for sample events and the classification facts for all others (deeper assessment and evidence withheld); full tier returns every field. Endpoint: https://warmthengine.com/mcp
- get_connections - Retrieve Coordination Connections (CCs) — the typed, directional relationships WEO records between events — optionally filtered by event (as source or target), type (1–7), or confidence (CC-V / CC-E / CC-A). For a single CC by its identifier, use `get_connection_by_id`. Each CC carries its id, source/target event IDs, type name + number, confidence, and direction; full tier — and either tier when an endpoint is a sample event — adds the evidence summary, evidence detail, and verification history. Endpoint: https://warmthengine.com/mcp
- get_actors - Retrieve whole Sovereign Capability Profile (SCP) actors — each with its designation (PAA / AIK / ACS / Participant), capability score, severance result, and a met/not-met assessment across the seven capability dimensions (D1–D7). Use to fetch complete actor records; to pivot one dimension across all actors, compare actors side by side, or read the dimension-watch register, use `query_scp`. Filter by designation or actor name. Free tier returns each dimension's met status and recorded headline (and the US sample in full); full tier adds the per-dimension constraint, qualification, and sources. Descriptive — recorded status, never inference. Endpoint: https://warmthengine.com/mcp
- get_coverage_stats - Retrieve the current corpus statistics — live counts and distributions of events, Coordination Connections (CCs), and Sovereign Capability Profile actors across bloc, tier, domain, event type, primary industry, CC type, confidence, and designation, plus Environmental Nexus Tag (ENT) statistics with the Warmth Engine Ratio, the event-ID range, and the methodology version. No parameters; figures are computed live, so the response always reflects the present database. The secondary-industry breakdown is full-tier only. Endpoint: https://warmthengine.com/mcp
- get_methodology - Look up the WEO methodology definition for any platform-specific term, field, or concept (e.g. "CC-V", "T2", "PAA", "ENT-1", "PIET"). Returns the term's definition, its section anchor, a deep link to that section of the published methodology, and the methodology version. Use to resolve any vocabulary the other tools return. Pass `term`; matching is exact-first, then substring, and an unknown term returns a sample of available terms. Endpoint: https://warmthengine.com/mcp
- get_connection_by_id - Retrieve a single Coordination Connection (CC) by its `connection_id` (e.g. "CC-06-11-3"). Use when you have the exact identifier; to list or filter CCs, use `get_connections`. Returns the CC with full evidence on the full tier — or when an endpoint is a sample event — and the base fields only otherwise. Endpoint: https://warmthengine.com/mcp
- get_topology - Retrieve the precomputed Coordination Topology — the structural lineage layer over the parent→child Coordination Connection graph (a DAG). Omit `node_id` for whole-graph network statistics (taxonomy-class counts, roots, multi-parent nodes, dominant roots by coordination reach, weakly-connected components). Pass `node_id` (e.g. "E34") for one node's structural metrics: generational depth (min/max/all-paths), coordination reach, directed betweenness, path diversity, fan-in/out, taxonomy class, component id. For the actual paths between nodes or up/down a lineage use `traverse_coordination`; for one event's value-chain stack use `get_event_stack`. Optional `class` / `cc_type` / `min_reach` filters return matching nodes. The full tier adds the held analyst layer (chain participation, curated orphan/sibling and named-feature sets). Endpoint: https://warmthengine.com/mcp
- traverse_coordination - Walk the Coordination Topology lineage graph (precomputed lookups over the parent→child Coordination Connection DAG). `mode="path"` returns every path between `source` and `target`, each with its CC-type (connection-type) sequence and whether it is pure lineage (homogeneous) or crosses a sibling/bidirectional edge; `mode="ancestors"`/`"descendants"` return the nodes reachable up/down the hierarchy; `mode="neighbours"` returns direct parents and children. For a node's structural metrics or the whole-graph summary rather than walks, use `get_topology`. `cc_types` (connection-type filter) and `max_depth` apply to `path` AND to the `ancestors`/`descendants`/`neighbours` adjacency walks — supplying either runs a bounded typed walk over the backbone edges. `homogeneous_only` is `path`-only (drops any path crossing a sibling edge); sent to an adjacency mode it is returned in `ignored_params`. A bare numeric `node_id` missing the `E` prefix is resolved (the canonical form is echoed as `resolved_node_id`); a node that exists but carries no backbone edges is reported as such rather than as unknown. Endpoint: https://warmthengine.com/mcp
- get_capability_signatures - Retrieve the precomputed Capability Signatures — directional Coordination Connection (CC) chains or hubs (connection types 1/3/4/5) whose member events span two or more Sovereign Capability Profile (SCP) dimensions, surfaced as corroborating structural texture rather than a headline finding. Omit `signature_id` for the whole set — each signature with its nodes, directional legs (from/to + connection type), dimension span, attribution profile, and narrative — plus metadata (the directional-edge inventory and the pre-operational caveat) and the non-signature same-capability clusters. Pass `signature_id` (e.g. "CS-001") for one. For the underlying event↔dimension membership links, use `get_capability_links`. A derived overlay over the directional CC graph; served whole and free. Endpoint: https://warmthengine.com/mcp
- get_capability_links - Retrieve the event↔dimension membership links — which events qualify or contribute to each actor's Sovereign Capability Profile (SCP) capability dimensions. Filter by `actor` (e.g. "US", "CN", "GB" — note GB, not UK), `dimension` (D1–D7), or `event_id`. Each link carries its `link_type` (`qualifying_contributor` = establishes the dimension vs `capability_area` = contributes to it), `attribution` (specific | general), and `entity` (the named asset, on qualifying links only); the full tier adds `qualification_basis`, `rationale`, and `note` (the deep qualification analysis). Sole-vs-multiple basis is derivable by counting `qualifying_contributor` links per actor×dimension (1 = sole; >1 = one of several) — links are never flattened to `qualifies:yes/no`, so the link-type and attribution distinctions return on both tiers. For the higher-order signatures built from these links, use `get_capability_signatures`. Endpoint: https://warmthengine.com/mcp
- get_threads - Retrieve Infrastructure Threads — the factual material-link layer recording where the same named AI hardware asset (chip / GPU / NPU / custom ASIC) appears as a documented fact in two events. A thread is not a Coordination Connection: no connection type, no confidence grade — either the asset match is verified or it isn't. Pass `event_id` for that event's linked events in both directions: outbound = assets this event deploys or trains on, each linking to its producer event; inbound = events that use this event's asset. Each link carries the sourced claim (`linkType` ∈ deploys | trains_on | powered_by | fabricated_at, plus the asset) and the host-event field that names it. Omit `event_id` for the whole layer. For one event's value-chain stack, use `get_event_stack`. Free on both tiers. Endpoint: https://warmthengine.com/mcp
- get_event_stack - Assemble the stack journey for one event — its kind-labelled value-chain neighbourhood at depth 1, the same composition the Atlas renders, in one call. Returns three separate arrays, never merged: `coordination` — the event's own Coordination Connections (CCs), all seven connection types, directed (types 1/3/4/5) and bidirectional/sibling (types 2/6/7) alike; each carries type/confidence/direction, plus evidence at full tier; `material` — the event's own Infrastructure-Thread edges, one per source→target pair, each with its sourced asset facts (`linkType` + asset + naming field); `capability` — the Sovereign Capability Profile (SCP) dimension-membership waypoints for the event itself (actor, dimension, link_type, attribution, entity; plus qualification_basis/rationale/note at full tier). The three are different kinds of claim: a thread is a factual asset match, not a CC, and is never rendered as one. A derived view over the existing connections, threads, and capability links — each substrate keeps its own gating, and the free tier leaks no paid fields. For the material layer alone, use `get_threads`; for the directed multi-hop coordination lineage between events, use `traverse_coordination`. Pass `event_id`. Endpoint: https://warmthengine.com/mcp
- query_scp - Query the Sovereign Capability Profile (SCP) register by pivoting and comparing — distinct from `get_actors`, which fetches whole actors. Choose exactly one mode: `dimension` (e.g. "D3") pivots that one dimension across every actor (each actor's met status and recorded headline, on what basis); `actors` (e.g. ["US","CN"]) lays those actors side by side across all seven dimensions (D1–D7); `watch:true` returns the `dimension_watch` register (forward-looking entries: actor, dimension, current vs expected_change, trigger, timeline). Readouts are descriptive — recorded status and fields, never causal inference. Free tier carries `met` + the headline for all actors and the US sample in full; the full tier adds the per-dimension evidence (constraint, qualification, sources, and `escalation_trigger` where recorded). Omit all three params for a usage hint. Endpoint: https://warmthengine.com/mcp
- get_blocs - Retrieve the WEO Bloc Membership Register — every nation in the register with its bloc assignment and universal membership category (Core / Integrated / Engaged / Peripheral / Non-Aligned), its key evidence and source URLs, plus document metadata and sectioned provenance (snapshot history, changelog, pre-register decisions). Served whole and free — the machine mirror of the public blocs register. A descriptive roster, never inference; the category definitions themselves are served by `get_methodology`. Endpoint: https://warmthengine.com/mcp

## Resources
- weo://journeys - WEO guided journeys — getting started Three worked starting points (coordination / material / stack) mapping to traverse_coordination, get_threads, get_event_stack. Same set the Atlas surfaces. MIME type: application/json

## Prompts
- journey_coordination - A2 · China generative-AI regulatory cascade Worked WEO starting point (coordination). What generative-AI services and rules cascade from China's Algorithm Recommendation Provisions? Maps to traverse_coordination. Read-only.
- journey_material - B1 · NVIDIA accelerator deployment hub Worked WEO starting point (material). Which supercomputers, data centres, and AI models run on NVIDIA's accelerators, and on which chip generation? Maps to get_threads. Read-only.
- journey_stack - C1 · Japan's subsidised GPU cloud across all layers Worked WEO starting point (stack). Which coordination, hardware, and capability layers meet at Sakura Internet's Ishikari GPU cloud? Maps to get_event_stack. Read-only.

## Metadata
- Owner: com.warmthengine
- Version: 1.3.0
- Runtime: Sse
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 28, 2026
- Source: https://registry.modelcontextprotocol.io