GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 4 days ago
Install
Warmth Engine Observatory
Overview
Description from the maker (original English)
Coordination Intelligence: AI infrastructure coordination dynamics across geopolitical blocs
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Developer tools
- You need to fill in: Authorization
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- Can do 18 things (tools) search_events, get_event, get_connections, get_actors …
- You fill in yourself:
Authorization
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http observatory https://warmthengine.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"observatory": {
"url": "https://warmthengine.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"observatory": {
"type": "http",
"url": "https://warmthengine.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
Authorizationsecret HTTP headerBearer token for analyst-tier access. Unauthenticated access receives free-tier data.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
search_eventsSearch 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_eventRetrieve 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_connectionsRetrieve 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_actorsRetrieve 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_statsRetrieve 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_methodologyLook 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_idRetrieve 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_topologyRetrieve 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_coordinationWalk 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_signaturesRetrieve 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_linksRetrieve 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_threadsRetrieve 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_stackAssemble 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_scpQuery 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_blocsRetrieve 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_contributionLook 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_metricsRetrieve 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_commitmentsRetrieve 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
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain warmthengine.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 244 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 18 tool descriptions and found no hidden instructions to the AI
Compared with others in Developer toolsi
- More stars than 0% of the other 4904 servers in this category
- Published to the registry more recently than 99% of the other 4904 servers in this category
- Basic checks equal to or better than 100% of the other 4904 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Warmth Engine Observatory safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.27.0) reached the registry today.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 16 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/mcpexposing 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/*andwarmthengine.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-readableerrata.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.