FirmTape Geo - public records of world events

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
84%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,638Tokens (definiciones de herramientas)
~1.6 KBTamaño de respuesta típico
Impacto moderado en la atención (1.28% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

https://geo.firmtape.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (7)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
⚪geo_records(since, until, sector, country, feed, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "ISO 8601 UTC start; default 7 days ago"
    },
    "until": {
      "type": "string",
      "description": "ISO 8601 UTC end; default now"
    },
    "sector": {
      "type": "string",
      "enum": [
        "gov",
        "air",
        "gps",
        "sea",
        "internet",
        "ground",
        "space",
        "attention"
      ],
      "description": "gov, air, gps, sea, internet, ground, space or attention"
    },
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, e.g. IR"
    },
    "feed": {
      "type": "string",
      "description": "feed id, or several separated by commas; the ids are listed by geo_sources"
    },
    "min_severity": {
      "type": "integer",
      "description": "1 keeps everything, 2 is notable and above, 3 is critical only"
    },
    "q": {
      "type": "string",
      "description": "words in the title"
    },
    "uid": {
      "type": "string",
      "description": "one record id, or several separated by commas; ignores the time window"
    },
    "limit": {
      "type": "integer",
      "description": "1 to 200, default 50"
    },
    "cursor": {
      "type": "integer",
      "description": "the next_cursor of a previous call"
    }
  }
}
🟢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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
⚪geo_coverage(since, until, days, sector, min_severity, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "ISO 8601 UTC start"
    },
    "until": {
      "type": "string",
      "description": "ISO 8601 UTC end; default now"
    },
    "days": {
      "type": "number",
      "description": "days back from until, instead of since; default 30, at most 365"
    },
    "sector": {
      "type": "string",
      "enum": [
        "gov",
        "air",
        "gps",
        "sea",
        "internet",
        "ground",
        "space",
        "attention"
      ],
      "description": "gov, air, gps, sea, internet, ground, space or attention"
    },
    "min_severity": {
      "type": "integer",
      "description": "1 keeps everything, 2 is notable and above, 3 is critical only"
    },
    "limit": {
      "type": "integer",
      "description": "how many countries, 1 to 250, default 50"
    }
  }
}
⚪geo_snapshot(country, since, until, days, limit)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, required, e.g. IR"
    },
    "since": {
      "type": "string",
      "description": "ISO 8601 UTC start"
    },
    "until": {
      "type": "string",
      "description": "ISO 8601 UTC end; default now"
    },
    "days": {
      "type": "number",
      "description": "days back from until, instead of since; default 7, at most 365"
    },
    "limit": {
      "type": "integer",
      "description": "how many records to return, 1 to 50, default 10"
    }
  },
  "required": [
    "country"
  ]
}
🟢geo_activity(country, sector, feed, min_severity, since, ...)

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.

Esquema de entrada

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

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, required, e.g. IR"
    },
    "id": {
      "type": "string",
      "description": "one series id from a previous answer, to return only that one"
    }
  },
  "required": [
    "country"
  ]
}
🟢geo_latency(feed, sector, country, since, until, ...)

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.

Esquema de entrada

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

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada7 herramientas
verificadoversión no registrada7 herramientas