> ## Documentation Index
> Fetch the complete documentation index at: https://worldmonitor.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP Overview
> Connect Claude, Cursor, and other MCP-compatible clients to WorldMonitor's live global-intelligence data via the Model Context Protocol.
WorldMonitor exposes its intelligence stack as a [Model Context Protocol](https://modelcontextprotocol.io) server so any MCP-compatible client (Claude Desktop, Claude web, Cursor, MCP Inspector, custom agents) can pull live conflict, market, aviation, maritime, economic, and forecasting data directly into a model's context.
**New here?** The [MCP Quickstart](/mcp-quickstart) is a five-minute path from zero to a real tool call in Claude Desktop. Come back to this page for auth modes, plans, OAuth setup, and the full tool catalog.
**Pro and API tiers can both connect via OAuth — no API key required.** Pro subscribers click *"Sign in with WorldMonitor Pro"* on the consent page; API Starter / Business / Enterprise users may sign in the same way OR paste a `wm_…` key. Free-tier users see a 401 at the OAuth step.
All paid tiers share the same MCP server and the same 39 tools. The current hard MCP daily reservation is enforced only for OAuth contexts at the Pro counter: **50 quota-consuming `tools/call` / `resources/read` calls per UTC day**. API-key (`wm_…`) MCP clients are protected by the **60 requests/minute/key** limiter in this handler; broader API Starter / Business REST allowances are enforced outside the MCP daily reservation path. (`describe_tool`, the v1.5.0 metadata-lookup helper, is exempt from the Pro daily quota.)
Pro subscribers can connect Claude Desktop / Cursor / claude.ai without ever pasting an API key — see [Pro sign-in flow](#pro-sign-in-flow) below. API Starter+ holders may continue to paste a `wm_…` key on the consent page (the original flow), or use the same OAuth path as Pro.
## Endpoints
| Endpoint | Purpose |
| --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `https://worldmonitor.app/mcp` | JSON-RPC server (Streamable HTTP transport; JSON responses by default, SSE responses when clients advertise `text/event-stream`; `initialize` defaults to protocol `2025-03-26`) |
| `https://api.worldmonitor.app/api/oauth/register` | Dynamic Client Registration (RFC 7591) |
| `https://api.worldmonitor.app/api/oauth/authorize` | OAuth 2.1 authorization endpoint (PKCE required) |
| `https://api.worldmonitor.app/api/oauth/token` | Token endpoint (authorization\_code + refresh\_token) |
| `https://api.worldmonitor.app/.well-known/oauth-authorization-server` | AS metadata (RFC 8414) |
| `https://worldmonitor.app/.well-known/oauth-protected-resource` | Resource server metadata (RFC 9728) |
Server identifier: `worldmonitor` v1.13.0.
Registry listings: the server is published in the [official MCP registry](https://registry.modelcontextprotocol.io/v0/servers?search=worldmonitor) as `app.worldmonitor/mcp` — a domain-verified namespace, so clients that resolve servers through the registry get the same endpoint and metadata as the server card above — and listed on [Smithery](https://smithery.ai/servers/worldmonitor/wm-mcp) and [mcp.so](https://mcp.so/server/world-monitor).
### Protocol negotiation
WorldMonitor's static server card at `/.well-known/mcp/server-card.json` advertises protocol version `2025-06-18`, and the live `initialize` handshake negotiates it by default — so the advertised floor and the negotiated version stay in lock-step:
* By default, `initialize` supports both `2025-03-26` and `2025-06-18`.
* Clients requesting `2025-06-18` receive `2025-06-18`; clients pinned to `2025-03-26` continue receiving `2025-03-26`.
* Setting `MCP_PROTOCOL_FLOOR_2025_06_18=off` pins the server back to the legacy `2025-03-26`-only floor; a client that then requests `2025-06-18` receives the safe default `2025-03-26`.
Tool `outputSchema` metadata is emitted on `tools/list` regardless of the negotiated protocol version. Older `2025-03-26` clients should ignore unknown fields, while newer clients can use the schema immediately.
### Streamable HTTP responses
WorldMonitor supports the Streamable HTTP POST flow with either JSON or SSE responses:
* Clients that omit `text/event-stream` from `Accept` receive the standard JSON-RPC JSON response body.
* Clients that send `Accept: application/json, text/event-stream` can receive a `text/event-stream` response for successful JSON-RPC POSTs.
* `initialize` SSE responses include `Mcp-Session-Id`; follow-up POSTs should send that same `Mcp-Session-Id` header.
* Each SSE response carries the JSON-RPC result as a single `message` event with an event `id`. There is no leading empty priming event — per the WHATWG SSE spec an empty `data:` field still dispatches a `message` (with `data === ""`), which causes strict handshake scanners to fail on `JSON.parse("")`.
* If the client disconnects after the sole event, it can reconnect by sending `GET /mcp` with `Accept: text/event-stream`, the same `Mcp-Session-Id`, and `Last-Event-ID`; resuming after the delivered event returns an empty stream. A client that dropped before receiving the event has no acknowledged `Last-Event-ID` and re-issues the POST instead.
* A **bare `GET /mcp`** — one **without** `Last-Event-ID` — is a client opening the optional standalone server→client SSE stream. This stateless edge route offers no server-initiated stream, so it answers `405 Method Not Allowed` (advertising `Allow`), which the MCP spec defines as the graceful "no standalone stream" signal. MCP SDK clients handle this transparently and complete the handshake; the `GET` verb itself is reserved for the authenticated `Last-Event-ID` replay above.
The replay buffer is in-memory and bounded per edge instance. Treat `Last-Event-ID` resume as loss-tolerant transport recovery, not durable message storage.
## Authentication
**Discovery is public.** `initialize`, `tools/list`, `resources/list`, `resources/templates/list`, and the `notifications/initialized` handshake are servable **without credentials**, so any agent (or agent-readiness scanner) can connect to `https://worldmonitor.app/mcp`, read the server identity, and enumerate the full tool and resource catalogs before authenticating — the same metadata already published in the static [server card](https://worldmonitor.app/.well-known/mcp/server-card.json). `tools/list`, `resources/list`, and `resources/templates/list` return only public catalog metadata (names, descriptions, URIs / URI templates — no data, no quota). `resources/read` of a **public** resource (a concrete, metadata-only freshness/health probe surfaced by `resources/list`, such as `worldmonitor://seed-meta/freshness`) is **also public and quota-free** — an anonymous agent can read it cleanly. Anonymous discovery is rate-limited to 60 requests/minute per client IP. Everything that returns data or spends quota (`tools/call`, and `resources/read` of a data-bearing **URI-template instantiation** — country risk, chokepoint status, market quote) — plus the gated metadata methods `prompts/list` and `logging/setLevel` — still requires one of the two auth modes below. A credential presented on a discovery method is still validated (a bad key returns `401`, never a silent anonymous downgrade).
The MCP handler accepts two auth modes, in priority order:
1. **OAuth 2.1 bearer** — `Authorization: Bearer ` where `` was issued by `/api/oauth/token`. This is what Claude Desktop, claude.ai, Cursor, and MCP Inspector use automatically. Required for any client that hits MCP from a browser origin.
2. **Direct API key** — `X-WorldMonitor-Key: wm_0123456789abcdef0123456789abcdef01234567` for user-issued keys, or an opaque operator-issued enterprise key. Intended for server-side scripts, `curl`, and custom integrations. Do **not** send an API key as a `Bearer` token — it will fail OAuth resolution and return `401 invalid_token`.
OAuth bearer requests re-check the resolved MCP token, user binding, and active entitlement before dispatch, so a subscription downgrade revokes OAuth MCP access on the next request. Direct `X-WorldMonitor-Key` requests validate the configured API key and then use the per-key limiter; their REST/API plan allowances are enforced outside the Pro/OAuth MCP daily reservation path.
### Redirect URI allowlist
Dynamic Client Registration is **not** open to arbitrary HTTPS redirects. Only these prefixes are accepted:
* `https://claude.ai/api/mcp/auth_callback`
* `https://claude.com/api/mcp/auth_callback`
* `http://localhost:` / `http://127.0.0.1:` (any port) — for Claude Code, MCP Inspector, local development
Other clients must proxy via one of these redirects or run locally.
### Token lifetimes
| Artifact | TTL |
| ------------------------ | ----------------- |
| Authorization code | 10 min |
| Access token | 1 hour |
| Refresh token | 7 days |
| Registered client record | 90 days (sliding) |
## Pro sign-in flow
Pro subscribers (and API Starter+ users who'd rather not paste a key) can authorize MCP clients via their existing WorldMonitor account — no API key needed.
1. **Add the server URL** in your MCP client. The canonical entrypoint is:
```
https://api.worldmonitor.app/mcp
```
(`https://worldmonitor.app/mcp` works too — it proxies the same handler.)
2. **Click "Sign in with WorldMonitor Pro"** on the consent page. This is the default CTA. You'll bounce through `worldmonitor.app/mcp-grant` (Clerk-protected — sign in if needed), then back to `api.worldmonitor.app/oauth/authorize-pro`, then to your client's redirect.
3. **Done.** No `wm_…` key is created or stored on your machine. The client receives a standard OAuth 2.1 access token (1 h TTL, 7 d refresh).
If you'd rather paste an API key (Starter+ / scripted clients), expand "Use API key instead" on the consent page and submit your `wm_` user key or operator-issued enterprise key — that path is unchanged.
### Daily limit (Pro tier)
* **50 quota-consuming calls per UTC day**, reset at 00:00 UTC.
* `tools/call` and `resources/read` of a data-bearing **URI-template instantiation** consume the Pro daily quota, except the metadata helper `describe_tool`.
* `initialize`, `tools/list`, `prompts/list`, `prompts/get`, `resources/list`, `resources/templates/list`, `logging/setLevel`, `notifications/initialized`, `ping`, and `describe_tool` do **not** count against the daily cap. `resources/read` of a **public** resource (a metadata-only freshness/health probe, e.g. `worldmonitor://seed-meta/freshness`) is likewise exempt — it carries no billable data.
* Hitting the cap returns JSON-RPC error `-32029` plus HTTP `429` with a `Retry-After` header pointing at the next UTC midnight.
* The cap is hard: concurrent `tools/call` or `resources/read` requests near the boundary use an atomic Redis reservation, so exactly the call that crosses 50 rejects.
Need higher-volume scripted access? **API Starter** and **API Business** add a `wm_…` key option plus REST/API plan allowances, but `wm_…` MCP calls are not metered by the MCP daily reservation counter; they still have the 60/minute/key MCP throttle. For batch or high-volume workflows, prefer the REST/API endpoints or contact Enterprise — see [Plans & limits](#plans--limits).
### Connected MCP clients
Each authorization mints a separate row, so revoking Claude Desktop does not affect Cursor.
* Manage connected clients in **[Settings → Connected MCP clients](https://worldmonitor.app/settings)**.
* See the live `clientName` (e.g. "Claude", "Cursor"), `lastUsedAt`, and `createdAt` per token.
* A revoke takes effect on the next MCP request (no positive cache).
* Up to **5 active tokens per user**. The 6th authorization silently revokes the least-recently-used existing one.
## Plans & limits
| Plan | MCP access | Auth modes | MCP daily reservation | Notes |
| ---------------- | ---------- | ----------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Free** | ❌ No | — | — | OAuth flow returns 401 `INSUFFICIENT_TIER`. Upgrade at [worldmonitor.app/pro](https://www.worldmonitor.app/pro). |
| **Pro** | ✅ Yes | OAuth only | **50 quota-consuming calls / UTC day** | Bounce-via-apex Clerk sign-in. No `wm_…` key needed or stored. |
| **API Starter** | ✅ Yes | OAuth **or** `wm_…` key | OAuth contexts use the Pro counter; `wm_…` MCP calls have **no MCP daily reservation** | Standard developer-tier REST/API access. |
| **API Business** | ✅ Yes | OAuth **or** `wm_…` key | OAuth contexts use the Pro counter; `wm_…` MCP calls have **no MCP daily reservation** | Higher REST/API throughput. |
| **Enterprise** | ✅ Yes | OAuth **or** `wm_…` key | Custom; `wm_…` MCP calls have **no default MCP daily reservation** | Custom SLA available. |
Per-minute throttling of 60 calls/minute/key (API-key clients) or 60/minute/user (OAuth contexts) protects against burst storms across all paid tiers. **The per-minute limiter runs before method dispatch, so every method (including `initialize`, `tools/list`, `prompts/list`, `resources/list`, `describe_tool`, etc.) counts toward 60/min.** Only the Pro/OAuth daily-quota cap is selective — that one is consumed exclusively by `tools/call` and `resources/read` reservations (see [Daily limit (Pro tier)](#daily-limit-pro-tier) above, and the [Error Catalog](/mcp-error-catalog#-32029--rate-limited-per-minute-or-daily) for the full method-exemption tables for both limits).
OAuth 60/min is per-USER (a user with 3 Claude installations shares one 60/min pool); API-key 60/min is per-KEY (multiple keys = higher throughput).
Hitting the Pro/OAuth daily quota returns JSON-RPC error `-32029` plus HTTP `429` with a `Retry-After` header pointing at the next UTC midnight. Hitting the per-minute limit returns the same error code with a short `Retry-After`.
### Other rate limits
* **OAuth authorize**: 10 requests / minute / IP
* **OAuth token**: 10 requests / minute / IP
* **Dynamic registration**: 5 registrations / minute / IP
Exceeding any limit returns HTTP `429` with a `Retry-After` header.
## Client setup
### Claude Desktop
`~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) — use the remote MCP entry:
```json theme={null}
{
"mcpServers": {
"worldmonitor": {
"url": "https://worldmonitor.app/mcp"
}
}
}
```
Claude Desktop handles the OAuth flow automatically on first connection.
### Claude web (claude.ai)
Add via **Settings → Connectors → Add custom connector**:
* Name: `WorldMonitor`
* URL: `https://worldmonitor.app/mcp`
### Cursor
`~/.cursor/mcp.json`:
```json theme={null}
{
"mcpServers": {
"worldmonitor": {
"url": "https://worldmonitor.app/mcp"
}
}
}
```
### MCP Inspector (debugging)
```bash theme={null}
npx @modelcontextprotocol/inspector https://worldmonitor.app/mcp
```
## Tool catalog
The server exposes 39 tools. Most are cache-reads over pre-seeded Redis keys (sub-second). The slower, non-cache paths are the six live LLM/external-API tools (`get_world_brief`, `get_country_brief`, `analyze_situation`, `generate_forecasts`, `search_flights`, `search_flight_prices_by_date`) plus the live geo RPC tools (`get_airspace`, `get_maritime_activity`), which proxy fresh aviation/maritime API calls with edge timeouts. One (`describe_tool`, added v1.5.0) returns the full uncompressed definition of any other tool — useful when the compressed `tools/list` description is ambiguous; exempt from the Pro daily quota.
For per-tool parameters, freshness budgets, timeouts, and concrete `curl` examples, see the [MCP Tools Reference](/mcp-tools-reference). For payload projection — every tool accepts an optional `jmespath` argument that typically cuts response size by 80-95% — see the [JMESPath guide](/mcp-jmespath).
### Markets & economy
| Tool | Description |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_market_data` | Equity quotes, commodity prices (incl. gold GC=F), crypto, FX, sector performance, ETF flows, Gulf markets. |
| `get_economic_data` | Fed Funds, economic calendar, fuel prices, ECB FX, EU yield curve, earnings, COT, energy storage, BIS DSR + property prices. |
| `get_country_macro` | IMF WEO bundle per country: inflation, current account, GDP/capita, unemployment, savings-investment gap (\~210 countries). |
| `get_eu_housing_cycle` | Eurostat annual house price index (prc\_hpi\_a), 10-yr sparkline per EU member + EA20/EU27. |
| `get_eu_quarterly_gov_debt` | Eurostat quarterly gross government debt (%GDP), 8-quarter sparkline. |
| `get_eu_industrial_production` | Eurostat monthly industrial production index, 12-month sparkline. |
| `get_prediction_markets` | Active Polymarket event contracts with live probabilities. |
| `get_supply_chain_data` | Dry bulk shipping stress index, customs flows, COMTRADE bilateral trade. |
| `get_tariff_trends` | Global trade and pricing indicators: US tariff trends (HTS-coded), BigMac index, FAO Food Price Index, and per-country national debt levels. |
| `get_chokepoint_status` | Live maritime chokepoint status: per-chokepoint vessel transit counts (10-min cadence), rolling transit summaries, per-port activity, plus static reference data and flow aggregates. Covers Suez, Hormuz, Malacca, Bab-el-Mandeb, Panama, etc. |
| `get_consumer_prices` | Per-country consumer-prices intelligence: 30-day overview, category-level inflation, retailer spread (essentials basket), top movers, and source freshness. Requires `country_code` (currently only `ae` is seeded). |
| `get_commodity_geo` | 71 major mining sites worldwide (gold, silver, copper, lithium, uranium, coal). |
### Energy
| Tool | Description |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_energy_intelligence` | Energy supply, prices, storage, disruptions, and policy: EIA petroleum stocks, electricity prices (Ember), gas storage (GIE), fuel shortages, fossil & renewable shares, active energy disruptions, government crisis policies. |
### Geopolitical & security
| Tool | Description |
| ----------------------- | ----------------------------------------------------------------------------------------------- |
| `get_conflict_events` | Active UCDP/Iran conflicts, unrest w/ geo-coords, country risk scores. |
| `get_country_risk` | CII score 0-100, component breakdown, travel advisory, OFAC exposure per country. Fast, no LLM. |
| `get_military_posture` | Theater posture + military risk scores. |
| `get_cyber_threats` | URLhaus/Feodotracker malware IOCs, CISA KEV catalog, active C2 infra. |
| `get_sanctions_data` | OFAC SDN entities + sanctions pressure scores by country. |
| `get_news_intelligence` | AI-classified threat news, GDELT signals, cross-source intel. |
| `get_positive_events` | Diplomatic agreements, humanitarian aid, peace initiatives. |
| `get_social_velocity` | Reddit r/worldnews + r/geopolitics top posts, engagement scores. |
### Movement & infrastructure
| Tool | Description |
| ------------------------------ | -------------------------------------------------------------------------------------------------------- |
| `get_airspace` | Live ADS-B over a country. Params: `country_code` (2-letter code), `type` (`all`/`civilian`/`military`). |
| `get_maritime_activity` | AIS density zones, dark-ship events, chokepoint congestion per country. Params: `country_code`. |
| `get_aviation_status` | FAA airport delays, NOTAM closures, tracked military aircraft. |
| `get_infrastructure_status` | Cloudflare Radar outages, major cloud/internet service status. |
| `search_flights` | Google Flights real-time search between IATA airport codes on a specific date. |
| `search_flight_prices_by_date` | Date-grid cheapest-day pricing across a range. |
### Environment & science
| Tool | Description |
| ----------------------- | ----------------------------------------------------------------------------------------------------------- |
| `get_natural_disasters` | USGS earthquakes, NASA FIRMS wildfires, hazard events. |
| `get_climate_data` | Temp/precip anomalies vs WMO normals, GDACS/FIRMS alerts, Mauna Loa CO2, OpenAQ PM2.5, sea ice, ocean heat. |
| `get_radiation_data` | Global radiation monitoring station readings + anomaly flags. |
| `get_research_signals` | Emerging technology events from curated research feeds. |
### Health
| Tool | Description |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `get_health_signals` | Active disease outbreaks (WHO/ECDC etc.) and global air-quality station readings (OpenAQ/WAQI PM2.5). For health-risk screening. |
### Humanitarian & displacement
| Tool | Description |
| ----------------------- | ------------------------------------------------------ |
| `get_displacement_data` | Refugee and IDP counts by country (UNHCR annual data). |
### AI intelligence (live LLM)
| Tool | Description | Cost |
| -------------------------- | ------------------------------------------------------------------------------------------------------------ | ----- |
| `get_world_brief` | AI-summarized world intel brief with structured source links. Optional `geo_context` param. | LLM |
| `get_country_brief` | Per-country geopolitical + economic assessment with structured source links. Supports analytical frameworks. | LLM |
| `analyze_situation` | Ad-hoc geopolitical deduction from a query + context. Returns confidence + supporting signals. | LLM |
| `generate_forecasts` | Fresh probability estimates (bypasses cache). | LLM |
| `get_forecast_predictions` | Pre-computed cached forecasts. Fast. | Cache |
## API coverage
An API endpoint is **MCP-exposed** only when the exact `METHOD /api/...` path is declared in a tool's registry `_apiPaths` entry. The table below is the human-facing rendering of those declarations from `api/mcp/registry/cache-tools.ts` and `api/mcp/registry/rpc-tools.ts`; it is narrower than the public OpenAPI catalog.
A REST route can exist in OpenAPI and still be REST-only. The parity test keeps that distinction explicit: every public OpenAPI operation must either appear in `_apiPaths` or be listed in `tests/mcp-api-parity.test.mjs` with a categorized exclusion reason.
Reverse lookup workflow:
1. Copy the exact method and path from the OpenAPI page, for example `GET /api/research/v1/list-tech-events`.
2. Search this table. If the route appears, call the listed MCP tool.
3. If it does not appear, the REST route is not exposed through MCP as an API-equivalent path. A cache-only MCP tool may still return related domain data, but it is not claiming that REST route.
4. For code-level verification, search `_apiPaths` in `api/mcp/registry/cache-tools.ts` and `api/mcp/registry/rpc-tools.ts`; the parity test explains intentional REST-only exclusions.
| MCP tool | API endpoints served |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `get_market_data` | `GET /api/market/v1/get-fear-greed-index`
`GET /api/market/v1/get-sector-summary`
`GET /api/market/v1/list-commodity-quotes`
`GET /api/market/v1/list-crypto-quotes`
`GET /api/market/v1/list-etf-flows`
`GET /api/market/v1/list-gulf-quotes`
`GET /api/market/v1/list-market-quotes` |
| `get_economic_data` | `GET /api/economic/v1/get-ecb-fx-rates`
`GET /api/economic/v1/get-economic-calendar`
`GET /api/economic/v1/get-eu-yield-curve`
`GET /api/economic/v1/list-fuel-prices`
`GET /api/market/v1/get-cot-positioning`
`GET /api/market/v1/list-earnings-calendar` |
| `get_tariff_trends` | `GET /api/economic/v1/get-fao-food-price-index`
`GET /api/economic/v1/get-national-debt`
`GET /api/economic/v1/list-bigmac-prices` |
| `get_energy_intelligence` | `GET /api/economic/v1/get-energy-crisis-policies`
`GET /api/supply-chain/v1/get-fuel-shortage-detail`
`GET /api/supply-chain/v1/list-energy-disruptions`
`GET /api/supply-chain/v1/list-fuel-shortages` |
| `get_consumer_prices` | `GET /api/consumer-prices/v1/get-consumer-price-freshness`
`GET /api/consumer-prices/v1/get-consumer-price-overview`
`GET /api/consumer-prices/v1/list-consumer-price-categories`
`GET /api/consumer-prices/v1/list-consumer-price-movers`
`GET /api/consumer-prices/v1/list-retailer-price-spreads` |
| `get_supply_chain_data` | `GET /api/supply-chain/v1/get-shipping-stress`
`GET /api/trade/v1/get-customs-revenue` |
| `get_chokepoint_status` | `GET /api/intelligence/v1/get-country-port-activity`
`GET /api/supply-chain/v1/get-chokepoint-status` |
| `get_climate_data` | `GET /api/climate/v1/get-co2-monitoring`
`GET /api/climate/v1/get-ocean-ice-data`
`GET /api/climate/v1/list-air-quality-data`
`GET /api/climate/v1/list-climate-anomalies`
`GET /api/climate/v1/list-climate-disasters`
`GET /api/climate/v1/list-climate-news` |
| `get_health_signals` | `GET /api/health/v1/list-air-quality-alerts`
`GET /api/health/v1/list-disease-outbreaks` |
| `get_conflict_events` | `GET /api/conflict/v1/list-iran-events`
`GET /api/conflict/v1/list-ucdp-events`
`GET /api/unrest/v1/list-unrest-events` |
| `get_news_intelligence` | `GET /api/intelligence/v1/list-cross-source-signals`
`GET /api/intelligence/v1/search-gdelt-documents` |
| `get_country_risk` | `GET /api/intelligence/v1/get-country-risk` |
| `get_country_brief` | `GET /api/intelligence/v1/get-country-intel-brief` |
| `get_social_velocity` | `GET /api/intelligence/v1/get-social-velocity` |
| `get_natural_disasters` | `GET /api/natural/v1/list-natural-events`
`GET /api/seismology/v1/list-earthquakes`
`GET /api/wildfire/v1/list-fire-detections` |
| `get_radiation_data` | `GET /api/radiation/v1/list-radiation-observations` |
| `get_infrastructure_status` | `GET /api/infrastructure/v1/list-internet-outages` |
| `get_airspace` | `GET /api/aviation/v1/track-aircraft`
`GET /api/military/v1/list-military-flights` |
| `get_maritime_activity` | `GET /api/maritime/v1/get-vessel-snapshot` |
| `get_military_posture` | `GET /api/military/v1/get-theater-posture` |
| `get_displacement_data` | `GET /api/displacement/v1/get-displacement-summary` |
| `get_positive_events` | `GET /api/positive-events/v1/list-positive-geo-events` |
| `get_sanctions_data` | `GET /api/sanctions/v1/list-sanctions-pressure`
`GET /api/sanctions/v1/lookup-sanction-entity` |
| `get_research_signals` | `GET /api/research/v1/list-tech-events` |
| `get_prediction_markets` | `GET /api/prediction/v1/list-prediction-markets` |
| `get_forecast_predictions` | `GET /api/forecast/v1/get-forecasts` |
| `get_world_brief` | `GET /api/news/v1/list-feed-digest`
`POST /api/news/v1/summarize-article` |
| `analyze_situation` | `POST /api/intelligence/v1/deduct-situation` |
| `search_flights` | `GET /api/aviation/v1/search-google-flights` |
| `search_flight_prices_by_date` | `GET /api/aviation/v1/search-google-dates` |
Tools with no declared API paths still return data via `tools/call`, but they should not be read as REST equivalents:
* **Cache-backed bootstrap aggregates** — read Redis keys seeded directly by Railway crons (e.g. `get_aviation_status`, `get_cyber_threats`, `get_country_macro`, the three EU Eurostat tools).
* **Static in-memory registries** — filter a constant bundled with the MCP server's edge binary, no upstream call at all (e.g. `get_commodity_geo`).
* **Live tools without a public OpenAPI row** — runtime proxies an HTTP call whose method drifts from the public spec, where a sibling tool already covers the spec-declared method (e.g. `generate_forecasts` POSTs `/api/forecast/v1/get-forecasts` while `get_forecast_predictions` owns the GET).
Common REST-only exclusions in `tests/mcp-api-parity.test.mjs`:
* **Mutating endpoints** — writes, queues, webhooks, cache refreshes, or persistent side effects. Example: `GET /api/aviation/v1/list-airport-delays` is intentionally REST-only because the GET handler refreshes/persists airport-delay cache state; `get_aviation_status` exposes the already-seeded cache-backed snapshot instead.
* **Fetch-on-miss endpoints** — may call paid or rate-limited upstreams when cache is cold. Examples: `GET /api/conflict/v1/list-acled-events`, `GET /api/infrastructure/v1/list-service-statuses`, and `GET /api/supply-chain/v1/get-critical-minerals`.
* **High-cardinality lookups** — arbitrary identifiers are not enumerable or cache-bundle friendly. Example: `GET /api/aviation/v1/get-flight-status`.
* **LLM-cost endpoints** — direct LLM passthroughs or fetch-on-miss paths with per-call model cost stay out of open MCP exposure unless wrapped by a purpose-built tool.
* **Deferred future tools** — pure reads whose cache keys are not yet exposed by an MCP bundle. Example: `GET /api/cyber/v1/list-cyber-threats` is slated for a future expanded-domain tool rather than claimed by today's cache-backed `get_cyber_threats`.
* **Manual mapping** — parameterized cache keys or inline Redis/Convex handlers need human triage. Examples: `GET /api/research/v1/list-arxiv-papers`, `GET /api/research/v1/list-trending-repos`, and `GET /api/research/v1/list-hackernews-items`; `get_research_signals` declares only `GET /api/research/v1/list-tech-events`.
See the [Tool catalog](#tool-catalog) above for the complete list of 39 tools, or the [MCP Tools Reference](/mcp-tools-reference) for per-tool details.
## Prompts and resources
In addition to the 39 tools, WorldMonitor exposes MCP prompts and resources so clients can discover common workflows and address stable data slices without inventing tool plans from scratch.
### Prompts
`prompts/list` returns six workflow templates. `prompts/get` renders the selected template into a user message with the right `tools/call` sequence and pre-baked JMESPath projections.
| Prompt | Purpose |
| -------------------- | -------------------------------------------------------------------------------------------------- |
| `country-briefing` | Country risk, AI intelligence brief, and macro indicators for one ISO 3166-1 alpha-2 country. |
| `energy-shock-watch` | Active energy disruptions, fuel shortages, and government crisis policies; optional country focus. |
| `market-open-prep` | Lightweight equity, commodity, and crypto mover briefing for a market-open scan. |
| `conflict-pulse` | Active UCDP conflict events plus alert-flagged top news, globally or for one country. |
| `route-risk-check` | Maritime chokepoint transit summary and risk posture for one chokepoint. |
| `freshness-audit` | Cache freshness check across market, energy, and chokepoint bootstrap envelopes. |
`prompts/list` and `prompts/get` are metadata/workflow discovery methods: they are exempt from the Pro daily quota, though they still count toward the 60/minute per-minute limiter.
### Resources
Resources come in two tiers. **Concrete resources** are surfaced by `resources/list` and read anonymously and quota-free; **URI templates** (parameterised, data-bearing) are surfaced by `resources/templates/list` and each concrete instantiation reads under auth + the Pro daily quota.
`resources/list` — concrete, anonymously readable, quota-free:
| Resource URI | Backing data |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `worldmonitor://seed-meta/freshness` | Market-data bootstrap freshness envelope only: `cached_at` and `stale`. A cheap health probe to detect a stuck seeder — no auth, no quota. |
`resources/templates/list` — parameterised URI templates. Substitute the placeholder, then `resources/read` the concrete URI (auth required; consumes the Pro daily quota symmetrically with the equivalent `tools/call`):
| Resource URI template | Backing data |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `worldmonitor://countries/{iso2}/risk` | Country risk score, component breakdown, travel advisory, and sanctions exposure. `{iso2}` is lowercase alpha-2, for example `de` or `us`. |
| `worldmonitor://chokepoints/{slug}/status` | Chokepoint transit summary and risk narrative. `{slug}` is one of the published kebab-case chokepoint slugs, such as `suez`, `strait-of-hormuz`, or `bab-el-mandeb`. |
| `worldmonitor://markets/{symbol}/quote` | Single-symbol market quote slice. `{symbol}` is uppercase, for example `AAPL`, `GC=F`, or `BTC-USD`. |
`resources/list` and `resources/templates/list` are metadata and do not consume the Pro daily quota. `resources/read` of a template instantiation intentionally consumes the same daily quota slot as the equivalent `tools/call`; it routes through the same dispatcher so a data-bearing resource cannot bypass the Pro cap. `resources/read` of a public (concrete) resource is quota-free — it returns only metadata. As with every MCP method, all of these still count toward the 60/minute limiter. For the exact `-32029` status/header differences between per-minute throttling and daily quota exhaustion, see the [MCP Error Catalog](/mcp-error-catalog#-32029--rate-limited-per-minute-or-daily).
### MCP Apps (interactive UI)
The server supports [MCP Apps](https://modelcontextprotocol.io/extensions/apps/build) (extension `io.modelcontextprotocol/ui`, spec `2026-01-26`) — interactive views a host renders in a sandboxed iframe when a linked tool is called. Three wire signals drive it:
* **`initialize`** declares support in the handshake. The response's `capabilities.extensions` names the extension: `{"io.modelcontextprotocol/ui": {}}`. This is the negotiation signal a host (or agent-readiness scanner) reads to classify the endpoint as an MCP-App surface — the `tools/list` and `resources/list` entries below are the content it then renders.
* **`tools/list`** advertises the linkage on the tool. `get_country_risk` carries `_meta.ui.resourceUri` (and the deprecated flat `ui/resourceUri` alias) pointing at its UI resource.
* **`resources/list`** surfaces the UI resource itself, alongside the concrete data resource (the parameterised data templates live in `resources/templates/list`):
| UI resource URI | mimeType | Renders |
| ------------------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `ui://worldmonitor/country-risk.html` | `text/html;profile=mcp-app` | The `get_country_risk` result as an interactive card: CII score, unrest/conflict/security/news component breakdown, travel-advisory level, and OFAC sanctions exposure. |
`resources/read` on a `ui://` URI returns the self-contained HTML view. Unlike the data resources, a `ui://` read is **public and quota-exempt** — the template carries no data and spends no upstream call, so a host can preload it (and an agent-readiness scanner can fetch it) without credentials and without touching the Pro daily cap. The view is fully self-contained (no external assets) and communicates with the host over the standard MCP Apps `postMessage` bridge (`ui/initialize` → `ui/notifications/tool-result` → `ui/notifications/size-changed`).
## JSON-RPC example
Server-side with a direct API key — send it as `X-WorldMonitor-Key`, **not** as a bearer token.
```bash theme={null}
WM_KEY="wm_0123456789abcdef0123456789abcdef01234567"
# 1. List tools
curl -s https://worldmonitor.app/mcp \
-H "X-WorldMonitor-Key: $WM_KEY" \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# 2. Call a cache tool
curl -s https://worldmonitor.app/mcp \
-H "X-WorldMonitor-Key: $WM_KEY" \
-H 'Content-Type: application/json' \
-d '{
"jsonrpc":"2.0","id":2,
"method":"tools/call",
"params":{"name":"get_country_risk","arguments":{"country_code":"IR"}}
}'
```
If instead you've completed the OAuth flow and hold an access token from `/api/oauth/token`, pass it as `Authorization: Bearer $TOKEN`.
## Response shape
Tool responses use the standard MCP content block format:
```json theme={null}
{
"jsonrpc": "2.0",
"id": 2,
"result": {
"content": [
{ "type": "text", "text": "{...json payload...}" }
],
"isError": false
}
}
```
For cache tools, the JSON payload includes `cached_at` (ISO timestamp of the oldest contributing data point) and `stale` (boolean — `true` when any contributing seed exceeded its per-key freshness budget) so the model can reason about freshness.
## Data freshness
All cache tools read from Redis keys written by Railway cron seeders. Typical freshness:
| Domain | Typical freshness |
| ---------------------- | ----------------- |
| Markets (intraday) | 1–5 min |
| Flights (ADS-B) | 1–3 min |
| Maritime (AIS) | 5–15 min |
| Conflicts / unrest | 15–60 min |
| Macro / BIS / Eurostat | daily–weekly |
| IMF WEO | monthly |
Seed-level health per key: [status.worldmonitor.app](https://status.worldmonitor.app/).
## Errors
The MCP handler signals failure on three independent layers — **HTTP status**, **JSON-RPC `error.code`**, and **soft-behavior envelopes inside `result.content[0].text`** — and a single failure can touch any combination.
| Layer | Common shapes | Where to look |
| ------------- | ------------------------------------------------------------------------------- | ------------------------------------------ |
| HTTP status | `200` (default for JSON-RPC), `401`, `429`, `503` | `WWW-Authenticate` / `Retry-After` headers |
| JSON-RPC | `-32001` auth · `-32029` rate-limited · `-32602` bad params · `-32603` internal | `error.code` + `error.message` |
| Soft envelope | `_budget_exceeded` (response too big), `_jmespath_error` (projection failed) | `result.content[0].text` parsed as JSON |
Triage from the outside in: HTTP status → JSON-RPC code → soft envelope. The full per-shape reference (trigger, paired status, recovery, example payload) lives in the [MCP Error Catalog](/mcp-error-catalog). A few high-frequency callouts:
* **401 + `-32001`** carries a `WWW-Authenticate` header with `resource_metadata` pointing at `/.well-known/oauth-protected-resource`. RFC 9728-aware clients re-run the OAuth flow on this header automatically.
* **429 + `-32029`** is the Pro daily cap (`Retry-After: `). The per-minute rate limit returns `-32029` inside HTTP 200, not 429 — see the catalog for the distinction.
* **Soft envelopes return HTTP 200** with no JSON-RPC `error` field — clients that inspect only the JSON-RPC layer will silently treat them as successes. Always parse `result.content[0].text` and check for a leading-underscore discriminator key (`_budget_exceeded`, `_jmespath_error`) before consuming the payload as data.
## Related
* [MCP Quickstart](/mcp-quickstart) — five-minute zero-to-first-call walkthrough
* [JMESPath guide](/mcp-jmespath) — projection grammar + 12 worked examples
* [MCP Tools Reference](/mcp-tools-reference) — per-tool parameters and `curl` examples
* [MCP Error Catalog](/mcp-error-catalog) — every JSON-RPC code, HTTP status, and soft envelope the server emits
* [Authentication overview](/authentication) — browser vs bearer vs OAuth
* [API Reference](/api-reference) — the same data via REST
* [Pro features](https://www.worldmonitor.app/pro)