Offnadir Delta MCP

What Off-Nadir-Lab/offnadir-delta-mcp does

Off-Nadir-Lab/offnadir-delta-mcp exposes the Off-Nadir Delta intelligence service through the Model Context Protocol. It is designed for OSINT, geopolitical-risk, and GEOINT workflows that need current information rather than a static knowledge snapshot.

The service returns geolocated event signals from global news media and other event sources, enriched with severity and GEOINT scores. Agents can inspect aggregate statistics, locate activity hotspots, read a Daily World Brief, examine claims and their evidence, and follow how an event changes over time. Event threads distinguish a newly detected event from a later update and preserve the basis used for an event's reported time.

How it works

The hosted endpoint is available at https://offnadir-delta.com/api/v1/mcp. Interactive clients can authenticate with OAuth 2.1 using PKCE and Dynamic Client Registration. The service also accepts bearer API keys, which are used by servers, CI workflows, and the local stdio package.

Imagery tools separate catalog discovery from interpretation. search_imagery returns metadata rather than pixels and labels scenes relative to an event. plan_event_imagery checks Sentinel-1 GRD and Sentinel-2 L2A against one event footprint and a pre/post window. Other tools rank imaging priorities, determine whether events are observable, and predict geometric satellite-access opportunities.

ask_analyst is asynchronous: it returns a job identifier while a background run continues. get_analyst_job retrieves its status and result. Reusing the same idempotency key avoids starting and charging a second run.

Setup and configuration

For a hosted connection, configure an MCP client with the endpoint URL and complete OAuth approval. The package includes documented connection paths for Claude, Cursor, VS Code, and Claude Code. Claude Code can register the endpoint with:

claude mcp add --transport http off-nadir-delta https://offnadir-delta.com/api/v1/mcp

For local stdio, run the package with Node.js through npx and provide OFFNADIR_DELTA_API_KEY:

{
  "mcpServers": {
    "off-nadir-delta": {
      "command": "npx",
      "args": ["-y", "offnadir-delta-mcp"],
      "env": { "OFFNADIR_DELTA_API_KEY": "ond_..." }
    }
  }
}

Docker can run the same package with the API key passed as an environment variable. The local package forwards tool calls to the hosted service and can expose the generated tool catalog without credentials.

Tools and capabilities

• Discover signals, daily briefs, statistics, hotspots, claims, developments, and event threads.
• Search imagery metadata and create deterministic plans for Sentinel-1 and Sentinel-2 observations.
• Rank imaging priorities, test event observability, and predict access opportunities across satellite families.
• Ask the Delta Analyst for a structured OSINT/GEOINT brief and retrieve asynchronous results.
• Create and manage watches, standing orders, monitored areas, notes, and account layer data.
• Check token balance and plan capabilities with get_usage before metered calls.

The service also exposes resources for the latest or dated brief, signal schema, current usage, system status, and watch data.

Limitations and notes

Calls follow usage-based token metering, although twelve of the twenty-three tools are free. Returned capabilities depend on the account plan. get_usage is available for pre-flight checks.

Imagery search provides metadata only. A predicted satellite pass is a geometric access opportunity, not an operator tasking commitment. In imagery results, a same-day scene is classified as same_day_unknown, not automatically as post-event, and a scene that only clips a bounding box is not treated as covering the event.

Standing-order costs apply when an answer changes rather than on every check. Paused standing orders still count toward the plan limit. Pausing a watch stops monitored-area measurement and standing-order checks; closing one requires a reason.