FirmTape Geo - public records of world events

com.firmtapePublished by firmtape.comOfficial publisherv1.0.0Updated Oct 24, 2026

Geopolitical OSINT: sanctions, NOTAMs, maritime warnings, outages, conflict records with sources

The publisher's own server: FirmTape - SPX, ES, NQ, RTY gamma levels, 100+ symbols

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP server giving assistants sourced public records of world events — sanctions, flight and maritime warnings, outages, conflict — plus coverage, latency

What you can do
Query public event records newest first: government advisories and sanctions, flight restrictions, maritime warnings, internet and grid outages, conflict, disaster and attention records, each with source, link and UTC timestamps, up to a year back. Inspect the feeds behind the records, including last response time, failure streak and record counts. See which countries appear in a window, with record and notable counts. Get a one-call country snapshot of counts by sector and feed, notable records and measured series against their normal. Read per-day record activity against a median baseline, and measured series such as aircraft, ships, GPS degradation, IPv4 space, fire clusters and night-lig
When to use it
Useful when an assistant needs sourced, timestamped situational awareness about a country or region — checking whether a quiet period is real, comparing activity against a baseline, or pulling sanctions, NOTAM and maritime warning records with links to their sources.
Requirements
A remote streamable HTTP endpoint; no local package. Requires a bearer token in the Authorization header, obtained from a FirmTape Geo API or Team plan. Network access to the endpoint is needed.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. Access is tied to a paid API or Team plan. Records are third-party public feeds and may be late, incomplete or backfilled; the server itself advises checking feed health before trusting a quiet window.

Installation

In SourceWeft

  1. Open FirmTape Geo - public records of world events in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.firmtape%2Fgeopolitical-osint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "firmtape-geo-public-records-of-world-eve": {
      "type": "http",
      "url": "https://geo.firmtape.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

8

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.

Parametersquidfeedlimitsinceuntilcursorsectorcountrymin_severity

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.

Takes no parameters.

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.

Parametersdayslimitsinceuntilsectormin_severity

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.

Parametersdayslimitsinceuntilcountryrequired

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.

Parametersdaysfeedsinceuntilsectorcountrymin_severity

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.

Parametersidcountryrequired

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.

Parametersdaysfeedsinceuntilsectorcountry

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.

Parametersidkindcountry

Version history

1
  1. v1.0.0LatestSep 17, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Firmtape integrations