# FirmTape Geo - public records of world events (remote · geo.firmtape.com)

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

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `geo.firmtape.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo.md), [page](https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo)

## Channel facts

- Endpoint: `https://geo.firmtape.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-firmtape-geopolitical-osint 'https://geo.firmtape.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-firmtape-geopolitical-osint": {
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-firmtape-geopolitical-osint": {
      "type": "http",
      "url": "https://geo.firmtape.com/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-firmtape-geopolitical-osint --url 'https://geo.firmtape.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-firmtape-geopolitical-osint:
    url: "https://geo.firmtape.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-firmtape-geopolitical-osint": {
      "Transport": "http",
      "Url": "https://geo.firmtape.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-firmtape-geopolitical-osint -t streamable-http -u 'https://geo.firmtape.com/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 62, +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.

### 2026-09-25 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 61, +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.

### 2026-09-22 (score 60, +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.

### 2026-09-21 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-20 (score 59, +31)

- [security regression] Authorization: fail → unverified
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-09-17 (score 28)

First indexed and scored.

## MCP tools (7)

### `geo_records` (~292 tokens)

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.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, e.g. IR
- `cursor` (integer): the next_cursor of a previous call
- `feed` (string): feed id, or several separated by commas; the ids are listed by geo_sources
- `limit` (integer): 1 to 200, default 50
- `min_severity` (integer): 1 keeps everything, 2 is notable and above, 3 is critical only
- `q` (string): words in the title
- `sector` (string): gov, air, gps, sea, internet, ground, space or attention
- `since` (string): ISO 8601 UTC start; default 7 days ago
- `uid` (string): one record id, or several separated by commas; ignores the time window
- `until` (string): ISO 8601 UTC end; default now

### `geo_sources` (~75 tokens)

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.

### `geo_coverage` (~186 tokens)

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.

Input parameters:

- `days` (number): days back from until, instead of since; default 30, at most 365
- `limit` (integer): how many countries, 1 to 250, default 50
- `min_severity` (integer): 1 keeps everything, 2 is notable and above, 3 is critical only
- `sector` (string): gov, air, gps, sea, internet, ground, space or attention
- `since` (string): ISO 8601 UTC start
- `until` (string): ISO 8601 UTC end; default now

### `geo_snapshot` (~167 tokens)

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.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2, required, e.g. IR
- `days` (number): days back from until, instead of since; default 7, at most 365
- `limit` (integer): how many records to return, 1 to 50, default 10
- `since` (string): ISO 8601 UTC start
- `until` (string): ISO 8601 UTC end; default now

### `geo_activity` (~223 tokens)

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.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, e.g. IR
- `days` (number): days back from until, instead of since; default 30, at most 365
- `feed` (string): feed id, or several separated by commas; the ids are listed by geo_sources
- `min_severity` (integer): 1 keeps everything, 2 is notable and above, 3 is critical only
- `sector` (string): gov, air, gps, sea, internet, ground, space or attention
- `since` (string): ISO 8601 UTC start
- `until` (string): ISO 8601 UTC end; default now

### `geo_series` (~181 tokens)

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.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2, required, e.g. IR
- `id` (string): one series id from a previous answer, to return only that one

### `geo_latency` (~259 tokens)

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.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, e.g. IR
- `days` (number): days back from until, instead of since; default 7, at most 90
- `feed` (string): feed id, or several separated by commas; the ids are listed by geo_sources
- `sector` (string): gov, air, gps, sea, internet, ground, space or attention
- `since` (string): ISO 8601 UTC start
- `until` (string): ISO 8601 UTC end; default now

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo#diagnostics

## Score history

- 2026-09-29: 63
- 2026-09-28: 63
- 2026-09-27: 62
- 2026-09-26: 62
- 2026-09-25: 61
- 2026-09-24: 61
- 2026-09-23: 60
- 2026-09-22: 60
- 2026-09-21: 59
- 2026-09-20: 59
- 2026-09-19: 28
- 2026-09-18: 28
- 2026-09-17: 28

## 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.

## Links

- Remote endpoint: https://geo.firmtape.com/mcp
- Authorisation metadata: https://geo.firmtape.com/.well-known/oauth-protected-resource/mcp
- Website: https://firmtape.com/geo
- Changelog RSS feed: https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo.json
- HTML version of this page: https://verifymcp.io/servers/com-firmtape-geopolitical-osint/geo