プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Warmth Engine Observatory

作者:warmthengineバージョン 1.27.0i★ –iクラウドで動く
レジストリ名com.warmthengine/observatory

インストール

概要

作者による説明(英語の原文)

Coordination Intelligence: AI infrastructure coordination dynamics across geopolitical blocs

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: クラウドで動く
  • トランスポート: Streamable HTTP
  • カテゴリ: その他
  • 入力が必要なもの:Authorization

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

このアドレスはリクエストの 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

  • このカテゴリのほかの32706件のうち0%よりスターが多い
  • このカテゴリのほかの32706件のうち100%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの32706件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Warmth Engine Observatoryは安全ですか?

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

入力が必要なもの:Authorization

パソコンで動きますか、それともクラウドですか?

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(1.27.0)がレジストリに届いたのは今日です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。

代わりに使えるものは?

同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Remote Desktop Commander

作者:desktop-commander

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

クラウドで動く★ 211一昨日更新
インストール

作者の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
PublicationDOI
WEO Methodology Manual — Operational specification covering event verification, significance assessment, tier classification, domain classification, industry tagging, environmental nexus tagging, and Coordination Connection methodology10.5281/zenodo.18427565
WEO Methodology Rationale — Companion document providing empirical derivation, theoretical grounding, and calibration justification for all methodology components10.5281/zenodo.18427582
Methodology Extensions
PublicationDOI
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 tiers10.5281/zenodo.18427586
WEO Contribution Architecture — Account of the platform's methodological contributions and their derivation10.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 challenges10.5281/zenodo.22785950
Self-Hosted Documentation

The V1.5 Manual and Rationale are self-hosted as navigable HTML with granular section anchoring:

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


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.

PopNxに聞く