FirmTape Geo - public records of world events

Last 30 days

Uptime

100%

Response time

115 ms typical, 115 ms slowest 5%

Last check

5 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "firmtape-geo-public-records-of-world-events": {
      "type": "http",
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}

7 tools

• 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 sa

• 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

• 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_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

• 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 tha

• 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

• 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 publ

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks