Off-Nadir Delta
Model Context Protocol

An MCP server for world event intelligence

Give your AI agent live, geolocated situational awareness. Over one MCP endpoint it can query world events, read the Daily World Brief, assess an event, and ask an analyst — sourced and geolocated, not a stale training snapshot.

Connect the MCP serverGet an API key

Quick Answer: The Off-Nadir Delta MCP server is a Model Context Protocol server that gives AI agents live, geolocated world event intelligence. Over a Streamable HTTP endpoint at /api/v1/mcp, an agent can call tools — query_signals, get_world_brief, assess_signal, ask_analyst — and use resources and prompts, all with a bearer API key, metered on your token balance. It works with Claude Code and any MCP client.

Tools

  • query_signals

    Query geolocated world event signals by area, date window, and category (metered).

  • get_world_brief

    Fetch the AI-synthesized Daily World Brief for the latest or a given date (free).

  • assess_signal

    Get an AI remote-sensing assessment for a single event — what to observe and which sensor to task (Pro).

  • ask_analyst

    Ask an OSINT/GEOINT question and get a structured, cited brief from an agentic analysis (Pro).

Resources

  • brief://latest

    The most recent Daily World Brief as a resource the agent can read directly.

  • brief://{date}

    A templated resource for any archived brief by date (YYYY-MM-DD).

  • signals://schema

    The signal object schema, so the agent knows every field it can reason over.

Prompts

  • daily-situation-briefing

    A ready-made prompt that produces a morning situation briefing from the latest signals.

  • assess-top-signal

    Surface the day’s highest-severity event and assess what to image next.

  • aoi-watch

    Watch an area of interest and summarize what changed and why it matters.

Connect it in one command

Issue a key from Account → Developer API, then add the server with your key. In Claude Code:

claude mcp add --transport http off-nadir-delta \
  https://offnadir-delta.com/api/v1/mcp \
  --header "Authorization: Bearer ond_..."

Any MCP client that supports HTTP transports works the same way — point it at https://offnadir-delta.com/api/v1/mcp and pass the Authorization header. The API & MCP reference has a ready-to-paste config block.

Keys are shown once and can be revoked anytime. Usage is metered on your token balance, so you stay in control of what an agent can spend.

From training snapshot to live awareness

A language model’s knowledge stops at its training cutoff. With this MCP server, an agent can ground its answers in what happened today — sourced, geolocated events and an analyst that cites its evidence — turning “I don’t have real-time information” into a specific, current assessment.

Frequently Asked Questions

What is the Off-Nadir Delta MCP server?▼
It is a Model Context Protocol (MCP) server that gives AI agents live, geolocated world event intelligence. Over a single Streamable HTTP endpoint (/api/v1/mcp), an MCP-capable agent can call tools to query events, read the Daily World Brief, assess an event, and ask an analyst — grounded in sourced, geolocated signals distilled from global news media rather than a static training snapshot. It also exposes resources and prompts so the agent has schema and ready-made workflows on hand.
Which tools, resources, and prompts does it expose?▼
Tools: query_signals and get_world_brief (available with API access), plus assess_signal and ask_analyst (Pro). Resources: brief://latest, the templated brief://{date}, and signals://schema. Prompts: daily-situation-briefing, assess-top-signal, and aoi-watch. Together they let an agent go from "what is happening in the world today" to a specific, sourced assessment without any custom integration code.
How do I connect it to Claude Code or another MCP client?▼
Issue an API key from Account → Developer API, then add the server as an HTTP transport with your key as a bearer header. In Claude Code: claude mcp add --transport http off-nadir-delta https://offnadir-delta.com/api/v1/mcp --header "Authorization: Bearer ond_…". Any MCP client that supports HTTP transports works the same way — point it at /api/v1/mcp and pass the Authorization header. The MCP page and /docs/api show a ready-to-paste config block.
Is it authenticated and metered?▼
Yes. The MCP server uses the same bearer API key as the REST API and is metered on your token balance: reading the brief is free, querying signals is billed per query, and the assessment and analyst tools are billed per call on Pro. Keys are issued and revoked from Account → Developer API, so you stay in control of what an agent can spend.
How is this different from just calling the REST API?▼
The REST API is for your own code; the MCP server is for AI agents. MCP standardizes how an agent discovers and calls tools, reads resources, and uses prompts — so instead of writing an integration, you register the server once and the agent can use the intelligence conversationally. Under the hood both hit the same data and the same token wallet. If you are wiring a dashboard or backend, use the REST API; if you are giving an assistant situational awareness, use MCP.

Related Resources

Event Intelligence API

The REST API behind the same intelligence

Learn more

API & MCP Reference

Full setup, tools, and config blocks

Learn more

Delta Agent

The in-app AI analyst the tools expose

Learn more

Delta Watchfloor

The dashboard behind the signals

Learn more

Daily Reports

The written daily assessment

Learn more

Satellite Intelligence for OSINT

The signal-to-satellite workflow

Learn more

Get an API key

Issue and manage keys

Learn more

Pricing

Plans, token metering, and access

Learn more

Give your agent situational awareness

Add the MCP server with your API key and let your agent query events, read the brief, and ask an analyst — grounded in live, sourced intelligence.

Connect the MCP serverSee the REST API