FirmTape Geo - public records of world events MCP Server
answering
FirmTape Geo - public records of world events is answering right now. Last checked 5 min ago. It exposes 8 tools.
Geopolitical OSINT: sanctions, NOTAMs, maritime warnings, outages, conflict records with sources
Uptime history
52 days of history · worst day 93%
52 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
140 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 11
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 September 2026. No other catalogue keeps this.
19 Oct
a tool appeared
geo_sites
20 Sep
a tool description was rewritten2 times that day
geo_series
19 Sep
5 tools appeared
geo_activity, geo_coverage, geo_latency and 2 more
19 Sep
2 tool descriptions were rewritten
geo_records, geo_sources
19 Sep
a tool changed the parameters it asks for
geo_records
and 1 more, back to 20 September 2026
Nothing serious here today
Today is the operative word: we check FirmTape Geo - public records of world events every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
run in your terminal
claude mcp add geopolitical-osint --transport http https://geo.firmtape.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://geo.firmtape.com/mcp~/.codex/config.toml
[mcp_servers.geopolitical-osint]
url = "https://geo.firmtape.com/mcp".cursor/mcp.json
{
"mcpServers": {
"geopolitical-osint": {
"url": "https://geo.firmtape.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"geopolitical-osint": {
"type": "http",
"url": "https://geo.firmtape.com/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
geo
geo_activity
Records per UTC day for a filter, and the median of the complete days before the last one, so a window can be read against its own normal. The day still being filled is returned apart and never averaged. Any feed that was switched on inside the window is named, because a rise that is only new feeds is not a busier world.
geo_coverage
Which countries the archive names in a window, with record and notable counts and the time of the last one, most notable first. Use it to pick a country before calling geo_snapshot or geo_records, instead of guessing one. A record naming several countries counts in each of them.
geo_latency
How long after a source published a record it reached us, per feed: the median, the 90th percentile and the worst case in seconds, over a window of up to 90 days. Rows found later in a source's own history are stamped backfill and counted apart rather than averaged in. Where publication_time_is_ours is true the source publishes no time of its own, so the record is stamped when we read it and the lag is zero by construction, not by speed. This measures our collection, not the news: almost every record here is public the minute it is published, and this product never claims to be ahead of the market.
geo_records
The records themselves, newest first: government advisories and sanctions, flight restrictions, maritime warnings, internet and grid outages, conflict, disaster and attention records. Up to a year back, each with its source, its link, its publication time and the time we first saw it, all UTC. Ask for one exact record with uid. For how many rather than which, call geo_activity; for one country in one call, geo_snapshot. Context, never a trading signal.
geo_series
The measured series for one country: aircraft overhead, military aircraft and degraded GPS by theatre, ships at sea in the Baltic and Norwegian areas our own AIS collectors watch hourly, ship transits through its chokepoints, routed IPv4 address space, fire clusters, night lights, PLA sorties around Taiwan and reading attention. Each carries its recent points, its own normal, the ratio between them, and normal_ready, which is false while the baseline is still too short to mean anything. A ratio is withheld with ratio_note where the normal is too small to divide by, as it is for the chokepoints that pass two or three ships a day.
geo_sites
Named energy sites and ports watched from orbit: refineries, oil terminals, LNG plants and fuel depots in Russia, Crimea and the Middle East, and ten oil ports. Without id, every site with its last thermal anomaly, its latest dated Sentinel-2 view and, for a port, its latest week of radar vessel counts. With id, one site in full: its thermal anomalies, its views (latest, and before and after each anomaly), 90 days of NASA FIRMS readings, and a port's weekly occupancy against its own normal. A thermal anomaly says a site read hotter than its own normal, never what caused it; a view is not evidence of damage.
geo_snapshot
One country in one call: its record counts by sector and by feed, its notable records, and every measured series that speaks about it against its own normal. This is geo_records, geo_activity and geo_series for a single country, counted, not written: no narrative, no score and no forecast.
geo_sources
Every feed behind the records: its id, its sector, when it last answered, its failure streak, and how many records it has in the served history. Read this before trusting a quiet window, because a feed that stopped answering is not a world that went calm. For how late each feed's records arrive, call geo_latency.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://geo.firmtape.com/mcp | streamable-http | answering | 129 ms | 5 min ago |
Alternatives to FirmTape Geo - public records of world events
same job, measured the same wayFuturistic Risk Intelligence
by cct15
Geopolitical conflict risk, political events, and maritime traffic data for AI agents
Nerai MCP
by serkvay13
Geopolitical grounding for AI agents: country risk, forecasts, chokepoints, sanctions. Free tier.
Proxy Republic
by proxyrepublic
AI world war on the real map: your agent commands a nation, signs pacts, betrays, and fights daily.
World Sense
by arcaneforecasting
Read-only live geopolitical-risk sensing for agents. ARCANE notices; never forecasts or advises.
RewindMap
by rewindmap
Historical borders and dated map events with source attribution and coverage limits.
W
Weather of Record
by weatherofrecord
Published weather records for a U.S. address and date, with provenance, and current NWS forecasts.
QSIG Intelligence
by qsig-x402
Geopolitical risk, theme board and point-in-time gold macro context for agents, paid via x402
A
AgentHub - Lean MCP Orchestrator
by propstreet
Enables coding agents to coordinate edits, reviews, and escalations without file locking conflicts
FirmTape Geo - public records of world events — questions
Answers built from our own checks of this server.
What can FirmTape Geo - public records of world events do?
It exposes 8 tools, read directly from the server on our last check. Among them: geo_activity, geo_coverage, geo_latency, geo_records, geo_series, geo_sites and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is FirmTape Geo - public records of world events working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 140 ms. The bar chart above shows every period we have measured.
How do I connect FirmTape Geo - public records of world events?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FirmTape Geo - public records of world events need an API key?
No. FirmTape Geo - public records of world events completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FirmTape Geo - public records of world events?
It answers our handshake in 140 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.