An MCP server for world event intelligence

Geolocated world events (geopolitical, security, disaster, infrastructure) from global news media, AI-enriched with severity/GEOINT scores and collection recommendations.

Roll-ups over the corpus: totals plus per-category and per-day breakdown.

Where activity concentrates: density grid-binned into ranked cells with peak severity, categories and representative event_ids.

The Daily World Brief — an AI digest of the previous UTC day.

What actually CHANGED about the events in an area, not which articles are new.

One event end to end: state plus every change in order — the "new event or update" distinction a feed cannot make.

Find a place in the location registry — ports, bases, airfields, power plants, chokepoints, named seas.

What has happened at one place: the registry record plus every linked event with HOW it was linked.

What else connects to one event, and what came before and after.

Search the imagery catalog (Sentinel-1, Sentinel-2, NISAR L-band) over an area and window.

The deterministic imagery plan for ONE event: checks BOTH sensors exactly once — sentinel-1-grd (SAR, the only look that survives cloud and night) and sentinel-2-l2a — against the event footprint and a pre/post window.

WHERE, and with what class of satellite, observation is most worthwhile now: composite IMPORTANCE crossed with the SPEC CLASS the required resolution demands — coarse, hr (free Sentinel-class) or vhr.

Which events a sensor can actually RESOLVE, over the FULL set.

WHEN a place can next be imaged and by WHAT: SGP4 over day-cached elements for 13 free-systematic and commercial-taskable families.

Given competing statements, the observation that would REFUTE the most — and those that would refute none.

Terrain height from the Copernicus DEM GLO-30 for a point, bbox or polygon, with relief — the number that governs SAR layover and shadow.

Compute FROM the terrain.

AI remote-sensing deep-dive for one signal: what to observe, sensors, a collection window.

Ask the Delta Analyst an OSINT/GEOINT question; returns a structured brief.

Status and result of an ask_analyst run.

The ledger of claims this key was given, each with its evidence class, independent source families and publishers.

Research one signal's location further and store a better coordinate if the sources genuinely narrow it.

Measure a spectral index over an area scene by scene through the Sentinel-2 archive.

Count vessel-like targets in ONE Sentinel-1 SAR scene by CFAR detection — radar sees through cloud and at night.

Put an area under CONTINUOUS watch: a question plus a bbox, re-answered on a schedule, notifying only when the answer changed.

The standing orders on this key: cadence, area, last check, last actual fire, and quiet_checks — a high quiet_checks means the watch is not earning its place.

Delete a standing order, or pause/resume with active=false/true.

Places under continuous satellite measurement: metric, latest value, change, anomaly flag, coverage.

One monitored area with its full measurement history.

Put a place under continuous satellite measurement — every new Sentinel-1/2 or VIIRS acquisition is measured.

The Watchlist as one list, each entry with a state bucket.

One watch end to end: target, state, latest change, measurements with recent series, standing-order questions, and for an event watch its verification state, developments and thread, plus this account's notes.

Everything needed to decide what to collect next about one watch, in one object.

Add a target to the Watchlist.

Rename, pause or resume a watch.

Delete a watch and its underlying resources — bound monitored areas with their history, and standing orders.

Add a note to a watch, start a thread, or reply.

Delete one note from a watch.

The layer sets saved on this account.

One saved layer set by id.

The data this account uploaded to the map, plus the formats the uploader accepts.

The calling key's remaining token balance and plan capabilities.