# com.thefilmmap/filming-locations (remote · thefilmmap.com)

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

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

## Components

- remote · `thefilmmap.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap.md), [page](https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap)

## Channel facts

- Endpoint: `https://thefilmmap.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-25.

- **Endpoint Security**: 57/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 8 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 is enforced; there's no plaintext access path.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1546 tokens (~193/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.thefilmmap/filming-locations MCP server?

com.thefilmmap/filming-locations is a hosted endpoint at https://thefilmmap.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-thefilmmap-filming-locations 'https://thefilmmap.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thefilmmap-filming-locations": {
      "url": "https://thefilmmap.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thefilmmap-filming-locations": {
      "type": "http",
      "url": "https://thefilmmap.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thefilmmap-filming-locations]
url = "https://thefilmmap.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thefilmmap-filming-locations": {
      "type": "remote",
      "url": "https://thefilmmap.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thefilmmap-filming-locations --url 'https://thefilmmap.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thefilmmap-filming-locations:
    url: "https://thefilmmap.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thefilmmap-filming-locations": {
      "Transport": "http",
      "Url": "https://thefilmmap.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thefilmmap-filming-locations -t streamable-http -u 'https://thefilmmap.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-thefilmmap-filming-locations": {
      "type": "http",
      "url": "https://thefilmmap.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-25 (score 76, 0)

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

### 2026-09-23 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “where_was_it_filmed” rewrote its description, which is the text the model reads

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “where_was_it_filmed” rewrote its description, which is the text the model reads

### 2026-09-20 (score 76, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 75, +1)

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

### 2026-09-17 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “where_was_it_filmed” rewrote its description, which is the text the model reads

### 2026-09-16 (score 74, +1)

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

### 2026-09-14 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “where_was_it_filmed” rewrote its description, which is the text the model reads

## MCP tools (8)

### `where_was_it_filmed` (~229 tokens)

Where a film, series or game was filmed

The main tool. Give a film or television title and get every place Wikidata records it as filmed at, with coordinates, plus the countries it records too coarsely to place. Covers 23,531 productions across 31,093 places. Two things to carry into any answer you write. First, video games AND anime are in here as well, and neither is filmed anywhere: their places are where they are SET (Wikidata P840, not P915), and every record says which through its `relation` field — never call one of those a filming location. Second, the gaps are real information: when `countries_only` is populated, Wikidata knows the production shot in those countries but not where, and the honest answer says so rather than guessing a street. This atlas never records which scene was shot where, so do not infer it.

Input parameters:

- `limit` (integer): Max places (default 50)
- `title` (string, required): Title, or its slug, e.g. "Skyfall", "game-of-thrones", "The Third Man"

### `search_productions` (~142 tokens)

Search films, series and games by name

Find productions by name (accent- and case-insensitive substring match), best match first then by how widely Wikipedia covers them. Filter by kind: film, tv, game or anime. Use it when you are unsure of a title before calling where_was_it_filmed. Games and anime are placed by where they are SET, never where they were filmed; the `relation` field on every result says which.

Input parameters:

- `kind` (string): Restrict to one medium (optional)
- `limit` (integer): Max results (default 10)
- `query` (string, required): Title or part of one, e.g. "bond", "star wars"

### `what_was_filmed_here` (~123 tokens)

What was filmed at a place

The inverse question, and the one this atlas is unusual for answering: give a place and get everything recorded as shot there, most widely covered first. Accepts a slug (preferred, e.g. "skellig-michael") or a name. Each result carries `relation`, because a video game or an anime attached to a place was SET there and not filmed there.

Input parameters:

- `limit` (integer): Max productions (default 50)
- `place` (string, required): Place slug (preferred) or name, e.g. "durham-cathedral"

### `search_locations` (~184 tokens)

Search filming locations by name

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.

Input parameters:

- `category` (string): Kind of place — key or slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & cities), re…
- `country` (string): Country name or ISO code (optional)
- `limit` (integer): Max results (default 10)
- `query` (string, required): Place name or part of one, e.g. "skellig", "petra"

### `locations_near` (~197 tokens)

Filming locations near a point

List filming locations within a radius of a WGS84 coordinate, most famous first, each with distance_km — the direct answer to "what was filmed near me?" and to set-jetting itineraries. Radius defaults to 50 km (max 500). Geocode the place yourself, then call this with its latitude and longitude.

Input parameters:

- `category` (string): Kind of place — key or slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & cities), re…
- `latitude` (number, required)
- `limit` (integer): Max results (default 15)
- `longitude` (number, required)
- `radius_km` (number): Search radius in km (default 50)

### `top_locations` (~209 tokens)

The most filmed places

The atlas ranked, worldwide or inside one country or one kind of place. Order is fame rank, which comes from the most widely covered production shot there — so rank 1 is the place the most famous production used, not the place with the most credits. Sort by `productions` instead to get the busiest places (Los Angeles, New York, Vancouver). Answers "most famous filming locations in <country>".

Input parameters:

- `category` (string): Kind of place — key or slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & cities), re…
- `country` (string): Country name or ISO code (optional — omit for worldwide)
- `limit` (integer): How many (default 10)
- `sort` (string): Ranking (default fame)

### `list_countries` (~79 tokens)

Countries with location counts

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.

### `get_statistics` (~69 tokens)

Atlas statistics

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 70
- 2026-08-31: 69
- 2026-08-30: 69
- 2026-08-29: 68
- 2026-08-28: 68
- 2026-08-27: 67

## Common questions

### What is the com.thefilmmap/filming-locations MCP server?

com.thefilmmap/filming-locations is an MCP server listed in the public MCP registry as com.thefilmmap/filming-locations. Where films and TV were shot, and where games, anime and manga are set. Wikidata, read only, CC0. This page covers its hosted endpoint (https://thefilmmap.com/mcp).

### Is the com.thefilmmap/filming-locations MCP server safe to use?

com.thefilmmap/filming-locations scores 76 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 com.thefilmmap/filming-locations MCP server expose?

com.thefilmmap/filming-locations exposes 8 tools: where_was_it_filmed, search_productions, what_was_filmed_here, search_locations, locations_near, and 3 more. Their descriptions and schemas cost roughly 1,232 tokens of context every time the server is loaded.

### Does the com.thefilmmap/filming-locations MCP server require authentication?

No. We connected to com.thefilmmap/filming-locations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.thefilmmap/filming-locations MCP server still maintained?

com.thefilmmap/filming-locations is still listed as active in the MCP registry. We last reached this channel on 25 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://thefilmmap.com/mcp
- Repository: https://github.com/Flightmussy/filmmap-mcp
- Website: https://thefilmmap.com/data/
- Changelog RSS feed: https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap.json
- HTML version of this page: https://verifymcp.io/servers/com-thefilmmap-filming-locations/thefilmmap