Compare
MCP Servers for Geopolitical Data
Direct answer: Self-hosted MCP packs wrap free APIs in scripts you must run, patch, and host. World Monitor is the hosted option: entitlements, quotas, OAuth, a published server-card, and an agent-skills index, so agents authenticate once and get governed access to live multi-domain data.
MCP servers for geopolitical data
Most "MCP servers for geopolitical data" are self-hosted wrappers around free upstreams. World Monitor is the hosted option: entitlements, quotas, OAuth, a published server-card, and an agent-skills index. Tool count is not our axis. Satellite MCP's 171 tools and world-intel-mcp's 120 tools beat us on that row, and the concession list says so before the rest of the page argues hosted access.
world-intel-mcp
world-intel-mcp is a MIT-licensed, self-hosted MCP surface over GDELT-derived events. It is free to clone. You run it, patch it, and absorb upstream rate limits. The win is a broad tool surface — on the order of 120 tools in public materials — and a license you can fork.
Pick it when you want to own the process and you are already in the GDELT universe. Pick a hosted server when you want OAuth, quotas, and someone else to keep the lights on.
Satellite MCP
Satellite MCP is the tool-count winner: on the order of 171 tools for imagery and passes, open source, self-hosted, cadence tied to pass schedules. It is not a multi-domain geopolitical server. It is a satellite workstation that speaks MCP.
Pick it for satellite-only agent workflows. Do not pick it as a hosted conflict-plus-AIS server; that is a different machine.
OSINT MCP
OSINT MCP exposes a wide OSINT tool surface (on the order of 64 tools) for self-hosters. Upstream dependent, open source, not a governed multi-domain data plane. The win is breadth of tools outside World Monitor's scope.
Pick it to give an agent a grab-bag of OSINT utilities. Pick World Monitor to give an agent one authenticated path into live scored feeds.
war-dashboard-data
A GDELT-based war dashboard you host, with MCP packaging in the same family as the firehose wrappers. Cadence follows GDELT's 15-minute batches. It is a conflict-event surface, not a fusion layer.
Pick it to self-host a GDELT war view. It will not give you entitlements, OAuth, or maritime and aviation in the same governed session.
GDELT Cloud MCP
Community MCP implementations on top of GDELT Cloud. The upstream is the 15-minute global news firehose and the 1979 archive. The MCP is not a GDELT-hosted product with a published enterprise SLA; it is community plumbing, labelled that way in the matrix.
Pick it for raw volume in an agent loop. Pick World Monitor for scored multi-domain access with a server-card you can point an agent at.
Off-Nadir Delta
Open-source, self-hosted imagery and geospatial tooling over public sources. Upstream dependent. The job is imagery workflows, not a hosted geopolitical data plane.
Pick it when the agent needs imagery tools you will run. It is not competing for the hosted multi-domain cell.
IMF PortWatch MCP
PortWatch is the free, authoritative chokepoint transit source (28 ports and chokepoints, IMF and Oxford). Community MCP implementations exist. The data is the win; hosting is still your problem unless you only consume the public API.
Pick PortWatch MCP for transit counts. Pick World Monitor when those counts have to sit next to conflict, aviation, and markets in one authenticated agent session.
Comparison matrix
| Product | Price | Update latency | Domains covered | Signup required | REST API | MCP server | Open source | Source count & licensing | Historical archive | Best for |
|---|---|---|---|---|---|---|---|---|---|---|
| World Monitor (hosted) | Free dashboard; MCP from $39.99/mo (Pro) | Source-dependent: live and minute-level feeds plus daily, weekly, and monthly datasets | Conflict, maritime AIS, aviation, markets, cyber, climate | No | From $99.99/mo (API Starter) | Yes (hosted, entitlements + quotas + OAuth) | AGPL-3.0 | 757 active providers, attributed public feeds | Live + rolling published snapshots | Hosted, governed multi-domain access for agents |
| world-intel-mcp | Free (MIT, self-hosted) | Upstream dependent | GDELT-derived event data | Self-host | GDELT-based | Yes (self-hosted) | MIT | Upstream public feeds | As retained | Self-hosted GDELT event surface |
| Satellite MCP | Free (open source, self-hosted) | Pass-schedule dependent | Satellite imagery and passes | Self-host | Upstream dependent | Yes (self-hosted) | Open source | Public satellite catalogs | As retained | Satellite pass scheduling for self-hosters |
| OSINT MCP | Free (open source, self-hosted) | Upstream dependent | OSINT tooling surface | Self-host | Upstream dependent | Yes (self-hosted) | Open source | Public OSINT sources | As retained | Broad OSINT tool surface for self-hosters |
| war-dashboard-data | Free (open source, self-hosted) | 15-minute batches (GDELT upstream) | Conflict event dashboards | Self-host | GDELT-based | Yes (self-hosted) | Open source | GDELT-derived feeds | GDELT archive depth | Self-hosted GDELT-based war dashboard |
| GDELT Cloud MCP | Free upstream; BigQuery for bulk | 15-minute global batches | Global news event firehose | No for REST; Google account for BigQuery | Yes | Yes (community implementation) | Open dataset (GDELT) | Global news ingestion | Archive to 1979 | Raw firehose volume in BigQuery |
| Off-Nadir Delta | Free (open source, self-hosted) | Upstream dependent | Imagery and geospatial tooling | Self-host | Upstream dependent | Yes (self-hosted) | Open source | Public imagery sources | As retained | Imagery tooling for self-hosters |
| IMF PortWatch MCP | Free | Event-triggered updates | 28 ports and chokepoints | No | Yes (API) | Yes (community implementation) | Open data (IMF + Oxford) | IMF and Oxford academics | Archived transit snapshots | Free authoritative chokepoint transit MCP |
How World Monitor measures this
World Monitor's MCP interface exposes source-backed datasets rather than making the language model the original observer. Maritime results draw on AISStream vessel observations and IMF PortWatch transit history; conflict context includes UCDP and ACLED; news views use GDELT. A tool response must be interpreted with the dataset's observation time and availability fields. Calling a tool now does not mean that every upstream measurement was made now.
GDELT ingestion follows 15-minute batches, ACLED requests use a 15-minute cache, and PortWatch transit history refreshes every 6 hours. Coverage differs by tool and source, even though they share an interface. The dated country snapshot below is a reproducible example of published risk context, not a guarantee that every MCP result has the same timestamp.
Coverage: the source catalog lists 757 active providers across the product, not per metric. Availability varies by source and location.
Published country instability snapshot, captured . This reference remains dated when live values change.
When to choose them instead
The self-hosted packs win the tool-count row outright, and it is not our axis: 171 and 120 tools beat our smaller hosted surface, stated openly.
- Satellite MCP (171 tools) wins on raw tool-count breadth for satellite-only workflows.
- world-intel-mcp (120 tools) wins on a broad MIT-licensed tool surface you can fork and self-host.
- OSINT MCP (64 tools) wins on a wide OSINT tool surface outside our scope.
- GDELT Cloud MCP wins on raw firehose volume and archive depth to 1979.
What to look for in a geopolitical MCP server
Separate hosted from self-hosted before you count tools. A 171-tool process you have to patch is not the same product as a smaller hosted surface with OAuth, quotas, and a server-card. If your team cannot run Node on a box, tool count is a vanity metric.
Score auth (OAuth versus a local stdio process), entitlements, documented quotas, whether the server-card is published, whether skills are indexed, and whether the upstream is one firehose or many attributed providers. Then score license and who files the bug when the wrapper breaks.
Demand an honest Unverified cell. Most third-party geopolitical MCP mentions are community wrappers. Labelling them "Yes" without "community" or "self-hosted" is how this category lies. World Monitor's cell is hosted with entitlements. The others on this page are self-hosted or community except where noted.
Skills and server-cards are not decoration. An agent that cannot discover the server will not use it. World Monitor publishes a server-card and an agent-skills index so discovery is a document, not a Slack message. Self-hosted packs publish READMEs, which is a different discovery path and a valid one if your team reads READMEs. Choose the discovery path you will actually maintain. A tool surface nobody can find is a 171-tool graveyard.
Why teams look for a hosted geopolitical MCP server
Agents showed up at work. A pile of stdio wrappers that each talk to one free API is fine for a weekend. It is not fine for a desk that needs one OAuth login, a quota, and a server-card an agent can discover. The search starts as "MCP servers for geopolitical data" because that is the protocol, not because the team wants 171 satellite tools.
The second trigger is operations. Someone has to patch the GDELT wrapper when the schema moves. Hosted access moves that job to a vendor with a catalog price. You pay $39.99/month at Pro and you lose the 171-tool row. That trade is the whole page.
How to use this MCP comparison
Inventory the agents first. If the agent needs satellite passes and imagery tools, Satellite MCP is the row and World Monitor is a sidecar. If it needs a GDELT firehose on a box you control, world-intel-mcp or war-dashboard-data is the row. If it needs chokepoint transits with IMF authority, PortWatch is the row. If it needs one OAuth login into scored conflict, maritime, aviation, and market feeds, World Monitor MCP is the row. Tool count is how you lose this bake-off: you will pick 171 tools and still not have entitlements.
Write the operations question into the RFP: who patches the wrapper when upstream schema moves. Self-hosted packs answer "we do." Hosted Pro answers "the vendor does, for $39.99/month." Both answers are legitimate. Mixing them up is how a demo full of tools becomes an unowned process in production. Keep Unverified cells unverified until a public server-card exists; do not let a README screenshot count as a hosted product.
Auth is the other split. A local stdio process with a personal API key is not OAuth with entitlements. Agents that will be shared across a team need the second. Agents that live on one laptop can use the first. World Monitor MCP is built for the shared case. Satellite MCP and OSINT MCP are built for the laptop-and-fork case. GDELT community MCP is built for the firehose case. If your proof-of-concept used stdio, do not assume production can keep that shape once two more people join the desk.
Why World Monitor wins on Hosted agent-native access
World Monitor is the hosted geopolitical MCP: entitlements, quotas, OAuth, a published server-card, and an agent-skills index over live multi-domain data. Agents authenticate once. You do not run the process. That is the cell self-hosted packs are not selling.
They still win tool count and the ability to fork for free. If your requirement is 171 satellite tools on a box you control, take Satellite MCP. If your requirement is governed multi-domain access, take the hosted server and stop scoring this as a hammer-versus-hammer fight.
The hosted cell also includes a documented quota. Self-hosted packs inherit whatever the upstream API will tolerate today, which is not a quota you can put in a contract. Agents that retry aggressively will discover that difference in production. Pro at $39.99/month is the price of not discovering it that way, plus OAuth and the server-card. It is not the price of 171 tools, and this page will not sell it as that. If you need both, run the satellite pack locally and authenticate the multi-domain session against the hosted server.
How these figures were checked
Prices and capability cells on this page were checked on 5 September 2026 from each named vendor's public pricing, product, or API documentation and from World Monitor's published catalog at /pricing, /mcp, and /compare/. Tool counts for Satellite MCP, world-intel-mcp, and OSINT MCP are the public figures used in this family's concessions. MCP cells are Yes (hosted), Yes (self-hosted), Yes (community implementation), or Unverified — never an unqualified Yes for a wrapper we did not verify. Where a vendor publishes a list price or quota, the matrix uses that figure. Where a vendor does not publish list pricing, the cell is "Undisclosed (enterprise-negotiated)". This family never substitutes a third-party estimate for a missing list price.
World Monitor prices on every row are the public catalog: $0 for the dashboard with no signup, Pro from $39.99/month including MCP access, and API Starter from $99.99/month for 1,000 requests/day. Third-party MCP status is Yes only when a public server or community implementation is documented; otherwise it is Unverified. Signup walls, archive depth, and domain coverage were read from product or docs pages. This page is committed copy with a dated lastmod. Vendors change SKUs, so re-check the linked vendor page before you buy.
Related reading
Related comparisons
Compare related tools by coverage, access requirements and workflow before choosing a monitoring setup.
Frequently asked questions
Which MCP server is best for geopolitical data?
World Monitor if you want hosted, governed access: entitlements, quotas, OAuth, a published server-card, and an agent-skills index over live multi-domain data. Self-hosted packs such as Satellite MCP (171 tools) and world-intel-mcp (120 tools) win on raw tool count and are free to fork.
Is there a hosted geopolitical MCP server?
Yes. World Monitor ships a hosted MCP server with entitlements, quotas, and OAuth, plus a published server-card and agent-skills index. Most alternatives are self-hosted scripts wrapping free APIs.
Do self-hosted MCP packs cost anything?
The packs themselves are free and open source, but they wrap free APIs with rate limits and require you to run the server. World Monitor MCP access starts at $39.99/month (Pro) with entitlements and quotas handled for you.
Is World Monitor MCP free?
No. MCP access starts at Pro, $39.99/month. The dashboard is free. Self-hosted packs are free as software and cost you operations.
Why concede 171 tools?
Because it is true. Satellite MCP's tool-count breadth is a real win for satellite-only workflows. We do not compete on that row.
Does World Monitor wrap GDELT only?
No. It curates 757 attributed providers across domains. GDELT-derived signals are in the mix, not the whole mix.
Can I point Claude or another agent at World Monitor MCP?
Yes. That is what a published server-card and OAuth are for. Confirm current auth docs at /mcp; this page is the comparison, not the live protocol spec.
Is a community GDELT MCP official?
No. It is labelled community implementation. GDELT Cloud is the upstream data; the MCP is plumbing.
Should I self-host and also buy Pro?
You can. Self-host the satellite or OSINT packs you need, and use World Monitor MCP for the governed multi-domain session. The page is a comparison, not a monopoly.
What does "Unverified" mean in the MCP column?
We could not cite a public MCP server or community implementation on the check date. It is not a "No." It is a refusal to guess.
Prices and capabilities were checked at publication time and can change. The comparison hub links every head-to-head page. Prices shown are from each vendor public pages or published reporting; enterprise figures marked undisclosed are negotiated and not published as list prices.