Skip to main content
Glama

FirmTape Geo - public records of world events

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation4/5

Tools are differentiated by aggregation level and scope: geo_records for individual records, geo_activity for daily counts, geo_series for country metrics, geo_sites for named facilities, and geo_snapshot as a country summary. Cross-references in descriptions direct the agent to the right tool. Minor overlap exists between geo_snapshot and the trio it summarizes, but descriptions clarify when to use each.

Naming Consistency5/5

All eight tools follow a consistent geo_ + noun pattern (geo_activity, geo_records, geo_series, etc.). No mixing of camelCase or verb styles. The convention is predictable and readable.

Tool Count5/5

Eight tools is well within the ideal 3-15 range. Each tool covers a distinct query dimension: records, counts, coverage, latency, series, sites, snapshot, sources. No obvious redundancy that would justify removing one.

Completeness4/5

The read-only archive domain is well-covered: records retrieval, feed health, latency, country coverage, measured series, and named sites. However, there is no clear tool for retrieving all records for a specific country or sector; geo_snapshot provides only counts and notable records. This minor gap can be worked around but may cause some agent friction.

Available Tools

8 tools
geo_activityAInspect

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.

Inputs: days, feed, since, until, +3 more.

geo_coverageAInspect

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.

Inputs: days, limit, since, until, +2 more.

geo_latencyAInspect

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.

Inputs: days, feed, since, until, +2 more.

geo_recordsAInspect

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.

Inputs: q, uid, feed, limit, +6 more.

geo_seriesAInspect

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.

Inputs: country (required), id.

geo_sitesAInspect

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.

Inputs: id, kind, country.

geo_snapshotAInspect

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.

Inputs: country (required), days, limit, since, +1 more.

geo_sourcesAInspect

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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with geopolitical risk intelligence, calibrated forecasts, sanctions and trade-control data, and live maritime chokepoint traffic across 60 countries, with source-linked answers.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Full-spectrum GEOINT server with 171 tools covering satellite imagery, aircraft tracking, maritime surveillance, military intelligence, conflict monitoring, environmental analysis, critical infrastructure, sanctions compliance, and cyber-geo intelligence from open-source data.
      100
      196 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      62 live, cryptographically signed data tools for AI agents and robots: weather, natural hazards, flights, shipping, space, CVEs, sanctions, software versions, sea ice and more. Every datapoint carries source, licence, timestamp and an Ed25519 signature.
      17 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources