All servers / News / Off-Nadir Delta MCP server
Off-Nadir Delta MCP server
Local (stdio) MCP server for Off-Nadir Delta — live, geolocated world-event intelligence, a Daily World Brief, satellite-imagery search, and an OSINT/GEOINT ana
Tested by ConnectATDScore 85 out of 100. Tested 2026-11-19 on package version 6.1.0. Package: offnadir-delta-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.4 seconds including download)
- Tools offered: 23
- Last published: 2026-11-16
- Weekly downloads (npm): 554
- License: Apache-2.0 · Direct dependencies: 1
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
query_signals18 of 25 parameters describedGeolocated world events from news, hazard feeds and satellite measurements, graded by the rule-based Delta GEOINT score (1-5); collection recommendations.
get_world_brief1 of 2 parameters describedAI world brief: daily (prior UTC day, all plans) or weekly/monthly by plan. freshness.is_stale: no newer day, so relay as stale.
get_usageno parametersThe calling key's remaining token balance and plan capabilities. Pre-flight a metered call with it.
search_imagery10 of 10 parameters describedSearch the imagery catalog over an area and window. Metadata only, no pixels. eventDate tags each scene pre/post — **a same-day scene is same_day_unknown, never post** — and eventPoint/eventAoi add target_relation, so a scene that only clips the bbox is not read as covering the event.
plan_event_imagery4 of 4 parameters describedThe deterministic imagery plan for ONE event: checks sentinel-1-grd (SAR, the only look that survives cloud and night) and sentinel-2-l2a exactly once each — plus NISAR L-band for flood_mapping (water under tall vegetation) — against the event footprint and a pre/post window. **A VHR recommendation never invalidates what the free catalog showed.**
rank_imaging_priority6 of 6 parameters describedWHERE, 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. Deterministic.
predict_satellite_passes7 of 7 parameters describedWHEN a place can next be imaged and by WHAT: 13 free-systematic and commercial-taskable families. **Every pass is a GEOMETRIC access opportunity** — no operator plan is consulted. retrieval_ok:false means timing is UNAVAILABLE, never "no passes".
assess_signal2 of 2 parameters describedAI remote-sensing deep-dive for one signal: what to observe, sensors, a collection window. Also returns a deterministic `context` whose `imagery_handoff.parameters` are the exact search_imagery inputs. Cached per signal; not-observable signals are rejected before any charge.
ask_analyst4 of 4 parameters describedAsk the Delta Analyst an OSINT/GEOINT question; returns a structured brief. **Durable async**: {status:"processing", job_id} comes back immediately and the run finishes in a background worker. Fetch with get_analyst_job, or re-send the SAME idempotencyKey (no second charge).
get_analyst_job1 of 1 parameter describedStatus and result of an ask_analyst run. Status is "processing", "done" or "error"; result_quality.status is **SEPARATE** — a done job can carry a partial result.
query_developments10 of 10 parameters describedWhat actually CHANGED about the events in an area, not which articles are new. Each change is labelled `world` (the event's own state moved), `measurement` (what we can see moved) or `interpretation` (the same reports re-processed — revised rules, a re-read — not new reporting). Plan-dependent values say so (`locked_by`).
get_event_thread1 of 1 parameter describedOne event end to end: state plus every change in order — the "new event or update" distinction a feed cannot make. `occurred_at_basis` distinguishes stated, absent and never measured. `sequence`: an event made of several incidents lists them (each with its geoint_level; highest_geoint_level is the highest, never a sum); an incident lists its parent and siblings. `measured_same_place`: measurements recorded at the same place close in time (a heat source, a transit change, SO2, a quake or cyclone) — the same place, not a confirmation or a cause. Plan-dependent: see `locked_by`, `plan_lock`.
list_watches3 of 3 parameters describedThe Watchlist as one list, each entry with a state bucket. `updated_since` returns only watches whose CONTENT changed after that instant — what a synchronised copy should poll.
list_notifications4 of 5 parameters describedWhat changed across the Watchlist, newest first: one row per change a watch reported, with read state. Reading does not mark them read. A value the plan does not open is `locked`, never filled in.
get_watch2 of 2 parameters describedOne watch end to end: target, state, latest change, measurements with recent series, standing-order questions, and for an event watch its stage, developments, imagery check and thread, plus this account's notes.
create_watch8 of 13 parameters describedAdd a target to the Watchlist. EVENT: the signal's event id binds the canonical event — **never watch an article URL**. AREA: a bbox. SITE: entity_id or lat+lon, and scale. VESSEL: vessel_key. Free to create; where the plan includes the collection section, a watched event's imagery is then checked at no token cost (up to 14 days).
update_watch6 of 6 parameters describedPause, resume or close a watch. **Pausing is not a display state**: monitored areas stop being measured and charged, standing orders stop checking. **Closing states how the question ended** (close_reason).
delete_watch1 of 1 parameter describedDelete a watch and its underlying resources — bound monitored areas with their history, and standing orders. To stop without losing them, pause with update_watch.
add_note8 of 8 parameters describedAdd a note to a watch, start a thread, or reply. **Confidence is what separates a note from a judgment**: with one it is a JUDGMENT that supersedes the previous judgment rather than overwriting it.
search_entities3 of 3 parameters describedFind a named place (airport, base, plant, port, dam, strait…) in any language or by IATA/ICAO code. Max 50.
get_entity1 of 1 parameter describedWhat has happened at one place: the registry record plus its most recent linked events, each with HOW it was linked. **`link_kind: proximity` is an association, not a statement that the event happened there.** Plan-dependent: see `plan_lock`.
get_related_events1 of 1 parameter describedThe relations recorded for one event: others at the same registry facility, naming the same place, or stored as the same campaign, each saying what is shared; plus reports merged into it. Merely-nearby events are not relations and are not returned. Plan-dependent: see `plan_lock`.
get_vessel3 of 3 parameters describedWhere a warship was reported in the last 30 days (official releases, U.S. Navy imagery), by vessel_key or the vessels an event names. **`line` joins observed points in date order — not the route sailed.** With neither: the roster — each observed ship's latest report and the ships not observed for 14+ days, counted against ships observed since the window start (not the full fleet). Positions are where it was reported, not where it is now. Plan-dependent: see `plan_lock`.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.