Is the Thefilmmap Filming Locations MCP server down?

mcp-registry/com.thefilmmap/filming-locations · v1.1.0

Also listed as awesome/flightmussy/filmmap-mcp, glama/flightmussy/filmmap-mcp-server

healthy
Last checked 2026-10-26 18:16 UTC · handshake 539ms

As of 2026-10-26 18:16 UTC, the Thefilmmap Filming Locations MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
4,871
outages (90d)
4
tools
8

Where films and TV were shot, and where games, anime and manga are set. Wikidata, read only, CC0.

Point your MCP client at this streamable-http endpoint: https://thefilmmap.com/mcp

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 8 tool(s); ~1,724 tokens of tool definitions.
Scores higher than 34% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~1,724 tokens per session — lighter than 60% of servers.
80 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions81
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_statistics, list_countries, locations_near, search_locations, search_productions and 3 more

2 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: locations_near

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations/fixes

get_statistics 1 change
{
  "name": "get_statistics",
  "description": "Headline figures computed live from the atlas: totals by medium and by kind of place, the top countries, the busiest and most famous locations, and — the number worth quoting — how many productions Wikidata records only at country level and therefore cannot place. The source for any aggregate claim about this dataset.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Atlas statistics"
}
list_countries 1 change
{
  "name": "list_countries",
  "description": "Every country in the atlas with how many filming locations it holds, most first — answers \"which country has the most filming locations\". Countries with a browsable page carry its URL. Coverage reflects what Wikidata records, which is uneven and skewed to Europe and North America, so read these as records and not as an inventory of world film production.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Countries with location counts"
}
search_locations 1 change
{
  "name": "search_locations",
  "description": "Find filming locations by name, optionally filtered by country (name or 2-letter ISO code) and by kind of place. Results are ordered by fame rank, which is driven by the most widely covered production shot there rather than by the place itself.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Max results (default 10)"
      },
      "query": {
        "type": "string",
        "description": "Place name or part of one, e.g. \"skellig\", \"petra\""
      },
      "country": {
        "type": "string",
        "description": "Country name or ISO code (optional)"
      },
      "category": {
        "type": "string",
        "description": "Kind of place — key or slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & cities), region (Countries & regions), fiction (Fictional places) (optional)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search filming locations by name"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.thefilmmap/filming-locations"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.thefilmmap/filming-locations"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations.svg)](https://glimind.com/server/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.thefilmmap%2Ffilming-locations?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:307b190aac623f2e…, first seen 2026-10-19, included at leaf 24804 of 74,650. Version history · verify what your client received.

Tools (8)

Compare: most reliable retrieval servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Thefilmmap Filming Locations MCP server down right now?

As of 2026-10-26 18:16 UTC, the Thefilmmap Filming Locations MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Thefilmmap Filming Locations MCP server provide?

Thefilmmap Filming Locations MCP server advertises 8 tools, including get_statistics, list_countries, locations_near, search_locations, search_productions.

How do I install Thefilmmap Filming Locations MCP server?

Point your MCP client at this streamable-http endpoint: https://thefilmmap.com/mcp

Is the Thefilmmap Filming Locations MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Thefilmmap Filming Locations MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve