Warmth Engine Observatory

MCP地图位置

提供方 warmthengine

地图位置 未标注 API Key 社区 / 第三方 CodexZed

AI infrastructure coordination intelligence. Read-only tools serve verified events, Coordination Connections, Sovereign Capability Profiles, and methodology with semantic anchor mappings. Open free tier plus a token-authenticated analyst tier.

一句话选型结论

按资料字段整理

Warmth Engine Observatory 属于地图位置类 MCP 服务器,传输方式未标注,API Key,可直接接入 Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类地图位置 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

地图位置
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

ai intelligence research mcp coordination infrastructure osint

支持客户端

适用场景

aiintelligenceresearch

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
地址与路线

查地址、算路线、找附近地点。

位置检索

按区域筛门店、站点与设施。

地理数据

拉取经纬度、行政区等地理信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在地图位置场景里让模型直接调用外部能力的人。
  • 已经在用 Codex、Zed 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Warmth Engine Observatory当前 未标注 未标注 未标注 无 未标注
MCP Server C2f246e3 20 stdio · 本地进程 本地部署 有 2026-05-17
OpenStreetMap MCP Server 12 stdio · 本地进程 本地部署 有 2026-05-18
Baidu Maps 10 stdio · 本地进程 本地部署 有 2026-05-17
Google Maps (google-maps-aa2563d3) 7 未标注 未标注 无 2026-05-17
generative-ai 未标注 stdio · 本地进程 本地部署 有 2026-04-17

服务器档案

地图位置
字段来自项目仓库与公开索引,中文说明由本站标注
提供方warmthengine上游标注的维护方 warmthengine
分类地图位置本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.9 KB
来自项目仓库与上游目录的原文,未做删改

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 (BSD-2-Clause) — Interactive map functionality
  • Leaflet.markercluster (MIT) — Map marker clustering
  • Geist (SIL Open Font Licence) — Primary typeface
  • Geist Mono (SIL Open Font Licence) — Monospace typeface
  • Cytoscape.js (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.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Warmth Engine Observatory 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Warmth Engine Observatory 怎么在 Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Warmth Engine Observatory 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Warmth Engine Observatory 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Warmth Engine Observatory 支持哪些客户端?

资料标注支持 Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Warmth Engine Observatory 能提供哪些能力?

资料显示能力标签包括 ai、intelligence、research、mcp、coordination、infrastructure。具体工具清单以官方文档为准。

Warmth Engine Observatory 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。