Warmth Engine Observatory

Name: Warmth Engine Observatory
Author: warmthengine

作者：warmthengine版本 1.27.0i★ –i在云端运行

注册名称com.warmthengine/observatory

安装

概览

作者提供的说明（英文原文）

Coordination Intelligence: AI infrastructure coordination dynamics across geopolitical blocs

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 开发者工具
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
可以做 18 件事（工具） search_events, get_event, get_connections, get_actors …
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 warmthengine.com 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 244 毫秒内响应（HTTP 200）
– 不适用
使用 OAuth 登录
无需登录
✓ 通过
工具描述中没有隐藏指令
已读取 18 个工具描述，未发现针对 AI 的隐藏指令

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 4907 个服务器的 0%
发布到注册中心的时间比此分类中其他 4907 个服务器的 98% 更新
基础检查结果等于或优于此分类中其他 4907 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Warmth Engine Observatory 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.27.0）于今天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.