WarStrikes in your AI assistant
The official WarStrikes connector lets Claude and other assistants read the live record of conflict reports, with every source linked. Read-only, free for public data, and with your API key for Events and Signals.
Connector address
Add this address as a custom connector (a remote MCP server) in any assistant that supports them:
https://warstrikes.com/mcpModel Context Protocol over Streamable HTTP. No sign-in for public data; nothing is written.
Add it
Claude
Settings → Connectors → Add custom connector. Name it WarStrikes and paste the address. Then ask, for example: “What has been reported near the Strait of Hormuz in the last 24 hours?”
Claude Code
claude mcp add --transport http warstrikes https://warstrikes.com/mcpWith a WarStrikes API key
Events and Signals need the key your organisation already uses for the API, sent as a header. In clients that accept headers:
claude mcp add --transport http warstrikes https://warstrikes.com/mcp --header "Authorization: Bearer wsk_…"Never put the key in the address. Keys are managed in the workspace; a key only reaches the layers your organisation has.
What it can do
| Tool | Access | What it returns |
|---|---|---|
search_reports | Free | Reports from the last 7 days, newest first: what a named public source reported, where and when, with the source type and location precision. Filter by words, region and type. |
get_report | Free | One public report by its id (the number in warstrikes.com/event/<id>-…), with its source, precision, the nearest infrastructure and nearby reports. |
get_daily_briefing | Free | The daily briefing for a UTC date (default: yesterday): what public sources reported that day, by region, every item linked to its report. |
list_regions | Free | The conflict regions WarStrikes follows, with report counts for the last 24 hours and 7 days and the region page. |
search_events | API key | Events: one occurrence linked to all the reports that describe it, with precision, entities, sectors and impacts. Same filters as GET /api/v1/events. |
get_event | API key | One Event by id, with its evidence and revision. |
search_signals | API key | Signals: WarStrikes assessments of severity, confidence and materiality. Same filters as GET /api/v1/signals, plus severity, confidence and materiality. |
get_signal | API key | One Signal by id. |
Every result names the source, its type (wire service, news outlet, official source or OSINT channel), how precisely the place is known, the WarStrikes page and the original source. There are no forecast tools.
Limits and terms
- Free tier: reports from the last 7 days, any public report by id, daily briefings and regions; up to 120 calls an hour per address.
- With a key: the rate limits and layers of your organisation’s plan, as for the API. Calls count as API usage.
- Answers should cite WarStrikes and the original source. Use follows the Data Use & API Policy; bulk copying of the archive is not allowed.
What assistants are told
The connector gives every assistant the same instructions:
WarStrikes is a live, source-linked record of reported strikes, explosions and military activity in conflict regions. Each report names its source and source type (wire service, news outlet, official source or OSINT channel) and how precisely its place is known. Describe items as reported by their source, with the time in UTC; do not present them as confirmed facts, and do not forecast. Link the WarStrikes page (url) and the original source (source_url) when you cite an item. Events and Signals need a WarStrikes API key; without one, use the report tools.