Warmth Engine Observatory

Name: Warmth Engine Observatory
Author: warmthengine

de warmthengineversión 1.27.0i★ –iSe ejecuta en la nube

Nombre en el registrocom.warmthengine/observatory

Instalar

Resumen

Descripción del creador (original en inglés)

Coordination Intelligence: AI infrastructure coordination dynamics across geopolitical blocs

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi3 de 3 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en la nube
Transporte: Streamable HTTP
Categoría: Otros
Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 3 de 3 superadas
Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
Puede hacer 18 cosas (herramientas) search_events, get_event, get_connections, get_actors …
Debes completar tú: Authorization

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Ejecuta esto en tu terminal

claude mcp add --transport http observatory https://warmthengine.com/mcp --header 'Authorization: your-value'

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "observatory": {
      "url": "https://warmthengine.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "observatory": {
      "type": "http",
      "url": "https://warmthengine.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

Authorization secreto HTTP header
Bearer token for analyst-tier access. Unauthenticated access receives free-tier data.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

search_events
Search and filter the WEO event corpus by `query` text 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 comp
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`. `date` is the implementation date (general availability for
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 c
get_actors
Retrieve whole Sovereign Capability Profile (SCP) actors — each with its designation (PAA / AIK / ACS / Participant), capability score, severance result, `assessed` (the register month, YYYY-MM, the profile was assessed in), a met/not-met assessment across the seven capability di
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 (E
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 r
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 ba
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, we
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 c
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 headl
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 `lin
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 — eit
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 connecti
query_scp
Query the Sovereign Capability Profile (SCP) register by pivoting and comparing — distinct from `get_actors`, which fetches whole actors and is where `energy_context` is served; it is not returned here. Pass exactly one of: `dimension` (e.g. "D3") pivots that one dimension across
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 (snapsho
get_contribution
Look up WEO Contribution Architecture vocabulary — the contributor programme's terms, credit classes, and governance provisions (e.g. "Delta Credit", "Founding Observer", "Observer Network", "rate card", "malinformation"). Returns the term's context, its section anchor, and a dee
get_metrics
Retrieve the WEO quantitative coordination metrics — dated observations of the documented connection network computed under Towards Coordination Science (TCS). Returns Cross-Sector Transmission Frequency (CSTF) with its permutation null model, the cross-sector transmission matrix
get_commitments
Retrieve the Compute Commitment Register — verified commitments of computing capacity by named actors to societal challenges, one record per instrument, quantities as published, never summed. Returns the challenge table (documents counted once per challenge touched; Committed and

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio warmthengine.com (el registro comprueba quién es dueño del dominio)
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
✓ Superada
El endpoint responde
Respondió en 244 ms (HTTP 200)
– No aplica
Inicio de sesión con OAuth
No hace falta iniciar sesión
✓ Superada
Sin instrucciones ocultas en las descripciones de herramientas
Leímos 18 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 32700 servidores de esta categoría
Publicado en el registro más recientemente que el 100% de los otros 32700 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 32700 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Warmth Engine Observatory?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: Authorization

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.27.0) llegó al registro hoy.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses

Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado anteayer

Instalar

Agent Data Tools: Utilities

de Nutshell2000

103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.

Se ejecuta en la nubeActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Warmth 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/mcp exposing 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/* 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 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-readable errata.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: warmthengine@proton.me

Acknowledgements

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

[Leaflet](https://leafletjs.com/) (BSD-2-Clause) — Interactive map functionality
[Leaflet.markercluster](https://github.com/Leaflet/Leaflet.markercluster) (MIT) — Map marker clustering
[Geist](https://vercel.com/font) (SIL Open Font Licence) — Primary typeface
[Geist Mono](https://vercel.com/font) (SIL Open Font Licence) — Monospace typeface
[Cytoscape.js](https://js.cytoscape.org/) (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.

Warmth Engine Observatory

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

Agent Data Tools: Utilities

README del creador

Warmth Engine Observatory (WEO)

Overview

Platform Components

Architecture

Methodology Documentation

Core Documentation

Methodology Extensions

Self-Hosted Documentation

Repository Structure

Citation

Contact

Acknowledgements

Licence