Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FirmTape Geo - public records of world events

REMOTE · GEO.FIRMTAPE.COM · SCANNED SEP 29

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

Available components

+3 this week 63 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1493 tokens (~213/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the FirmTape Geo - public records of world events MCP server?

FirmTape Geo - public records of world events is a hosted endpoint at https://geo.firmtape.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · geo.firmtape.com

# add to Claude Code
claude mcp add --transport http com-firmtape-geopolitical-osint 'https://geo.firmtape.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-firmtape-geopolitical-osint": {
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-firmtape-geopolitical-osint": {
      "type": "http",
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-firmtape-geopolitical-osint]
url = "https://geo.firmtape.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-firmtape-geopolitical-osint": {
      "type": "remote",
      "url": "https://geo.firmtape.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-firmtape-geopolitical-osint --url 'https://geo.firmtape.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-firmtape-geopolitical-osint:
    url: "https://geo.firmtape.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-firmtape-geopolitical-osint": {
      "Transport": "http",
      "Url": "https://geo.firmtape.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-firmtape-geopolitical-osint -t streamable-http -u 'https://geo.firmtape.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-firmtape-geopolitical-osint": {
      "type": "http",
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 20 Sept 26 +31
    • Authorization: fail → unverified ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 17 Sept 26 28

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://geo.firmtape.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=firmtape.com CN=WE1,O=Google Trust Services,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 709a82550e71f0880e8156e9ee25725e
SANs: firmtape.com, geo.firmtape.com, *.geo.firmtape.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of geo.firmtape.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
firmtape.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geo.firmtape.com/mcp Verified 200
http (plaintext) http://geo.firmtape.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~1,383 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
geo_activity ~223

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2, e.g. IR
daysnumber–days back from until, instead of since; default 30, at most 365
feedstring–feed id, or several separated by commas; the ids are listed by geo_sources
min_severityinteger–1 keeps everything, 2 is notable and above, 3 is critical only
sectorstring–gov, air, gps, sea, internet, ground, space or attention
sincestring–ISO 8601 UTC start
untilstring–ISO 8601 UTC end; default now

No output schema declared.

No examples provided.

geo_coverage ~186

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.

NameTypeReqDescription
daysnumber–days back from until, instead of since; default 30, at most 365
limitinteger–how many countries, 1 to 250, default 50
min_severityinteger–1 keeps everything, 2 is notable and above, 3 is critical only
sectorstring–gov, air, gps, sea, internet, ground, space or attention
sincestring–ISO 8601 UTC start
untilstring–ISO 8601 UTC end; default now

No output schema declared.

No examples provided.

geo_latency ~259

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2, e.g. IR
daysnumber–days back from until, instead of since; default 7, at most 90
feedstring–feed id, or several separated by commas; the ids are listed by geo_sources
sectorstring–gov, air, gps, sea, internet, ground, space or attention
sincestring–ISO 8601 UTC start
untilstring–ISO 8601 UTC end; default now

No output schema declared.

No examples provided.

geo_records ~292

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2, e.g. IR
cursorinteger–the next_cursor of a previous call
feedstring–feed id, or several separated by commas; the ids are listed by geo_sources
limitinteger–1 to 200, default 50
min_severityinteger–1 keeps everything, 2 is notable and above, 3 is critical only
qstring–words in the title
sectorstring–gov, air, gps, sea, internet, ground, space or attention
sincestring–ISO 8601 UTC start; default 7 days ago
uidstring–one record id, or several separated by commas; ignores the time window
untilstring–ISO 8601 UTC end; default now

No output schema declared.

No examples provided.

geo_series ~181

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.

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2, required, e.g. IR
idstring–one series id from a previous answer, to return only that one

No output schema declared.

No examples provided.

geo_snapshot ~167

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.

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2, required, e.g. IR
daysnumber–days back from until, instead of since; default 7, at most 365
limitinteger–how many records to return, 1 to 50, default 10
sincestring–ISO 8601 UTC start
untilstring–ISO 8601 UTC end; default now

No output schema declared.

No examples provided.

geo_sources ~75

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the FirmTape Geo - public records of world events MCP server?

FirmTape Geo - public records of world events is an MCP server listed in the public MCP registry as com.firmtape/geopolitical-osint. Geopolitical OSINT: sanctions, NOTAMs, maritime warnings, outages, conflict records with sources. This page covers its hosted endpoint (https://geo.firmtape.com/mcp).

Is the FirmTape Geo - public records of world events MCP server safe to use?

FirmTape Geo - public records of world events scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the FirmTape Geo - public records of world events MCP server expose?

FirmTape Geo - public records of world events exposes 7 tools: geo_records, geo_sources, geo_coverage, geo_snapshot, geo_activity, and 2 more. Their descriptions and schemas cost roughly 1,383 tokens of context every time the server is loaded.

Does the FirmTape Geo - public records of world events MCP server require authentication?

No. We connected to FirmTape Geo - public records of world events without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FirmTape Geo - public records of world events MCP server still maintained?

FirmTape Geo - public records of world events is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.