Movie Scene Map
REMOTE · MOVIESCENEMAP.COM
Where films and TV were shot, and where games, anime and manga are set. Wikidata, read only, CC0.
Available components
Last scanned (14 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1518 tokens (~189/item across 8 items; 8 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- 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 security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 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.
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 21 Nov 2026 · Probed https://moviescenemap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moviescenemap.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8cd0ec3d9a664040138840b317f8d5e2 |
| SANs: moviescenemap.com, *.moviescenemap.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 secure
Validation of moviescenemap.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| moviescenemap.com. | DS published | 2371 | 13 | Verified |
| moviescenemap.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://moviescenemap.com/mcp | Verified | 200 | |
| http (plaintext) | http://moviescenemap.com/mcp | HTTPS enforced | 301 | https://moviescenemap.com/mcp |
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 →
get_statistics Atlas statistics ~54
Headline figures computed live from the atlas: totals by medium and by kind of place, the top countries, the busiest and the most famous locations, and how many productions Wikidata records only at country level and so cannot place.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_countries Countries with location counts ~68
Lists every country in the atlas with its number of filming locations, most first. Countries with a page on the site carry its URL. The counts reflect what Wikidata records, which is uneven and skewed to Europe and North America: they are records, not an inventory of world film production.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locations_near Filming locations near a point ~194
Lists the filming locations within a radius of a WGS84 coordinate, most famous first, each with its `distance_km`: what was filmed near a point. The radius defaults to 50 km (at most 500). Takes a latitude and a longitude in degrees; it does not look up place names.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kind of place, as a key or a slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & citie… |
| latitude | number | yes | – |
| limit | integer | – | Max results (default 15) |
| longitude | number | yes | – |
| radius_km | number | – | Search radius in km (default 50) |
No output schema declared.
No examples provided.
search_locations Search filming locations by name ~187
Finds filming locations by name, optionally filtered by country (a name or a two letter ISO code) and by kind of place. Results are ordered by fame rank, which comes from the most widely covered production shot there rather than from the place itself.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kind of place, as a key or a slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & citie… |
| country | string | – | Country name or ISO code (optional) |
| limit | integer | – | Max results (default 10) |
| query | string | yes | Place name or part of one, e.g. "skellig", "petra" |
No output schema declared.
No examples provided.
search_productions Search films, series and games by name ~132
Finds productions by name, ignoring accents and case, best match first, then by how widely Wikipedia covers them. An optional filter by kind: film, tv, game, anime or manga. Each result carries its kind, its year and a `relation` field: films and series are placed where they were filmed, games, anime and manga where they are set.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Restrict to one medium (optional) |
| limit | integer | – | Max results (default 10) |
| query | string | yes | Title or part of one, e.g. "bond", "star wars" |
No output schema declared.
No examples provided.
top_locations The most filmed places ~217
Ranks the places in the atlas, worldwide or inside one country or one kind of place. The default 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. With `sort` set to `productions` the order is by number of productions (Los Angeles, New York, Vancouver).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kind of place, as a key or a slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & citie… |
| country | string | – | Country name or two letter ISO code (optional; without it the ranking is worldwide) |
| limit | integer | – | How many (default 10) |
| sort | string | – | Ranking (default fame) |
No output schema declared.
No examples provided.
what_was_filmed_here What was filmed at a place ~114
Returns everything recorded as made at a place, most widely covered first. Takes the place as a slug (e.g. "skellig-michael") or as a name. Each result carries a `relation` field, because a video game, an anime or a manga tied to a place is set there, not filmed there.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max productions (default 50) |
| place | string | yes | Place slug (preferred) or name, e.g. "durham-cathedral" |
No output schema declared.
No examples provided.
where_was_it_filmed Where a film, series or game was filmed ~207
Returns every place recorded for a film, series, game, anime or manga, with coordinates, plus the countries recorded too coarsely to place. Covers 45,158 productions across 41,131 places. Films and series are placed where they were filmed (Wikidata P915). Video games, anime and manga are filmed nowhere, so they are placed where they are set (P840); the `relation` field of each record says which. A filled `countries_only` list means Wikidata records the production in those countries without a finer place. Places named only in the production's own Wikipedia article come in separate fields prefixed `wiki_`. The data records that a production was filmed at a place, not which scene was shot there.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max places (default 50) |
| title | string | yes | Title, or its slug, e.g. "Skyfall", "game-of-thrones", "The Third Man" |
No output schema declared.
No examples provided.
How do I install the Movie Scene Map MCP server?
Movie Scene Map is a hosted endpoint at https://moviescenemap.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 · moviescenemap.com
claude mcp add --transport http com-moviescenemap-filming-locations 'https://moviescenemap.com/mcp'
What is the Movie Scene Map MCP server?
Movie Scene Map is an MCP server listed in the public MCP registry as com.moviescenemap/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://moviescenemap.com/mcp).
Is the Movie Scene Map MCP server safe to use?
Movie Scene Map scores 80 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 Movie Scene Map MCP server expose?
Movie Scene Map 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,173 tokens of context every time the server is loaded.
Does the Movie Scene Map MCP server require authentication?
No. We connected to Movie Scene Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Movie Scene Map MCP server still maintained?
Movie Scene Map is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Movie Scene Map MCP server?
VerifyMCP ran 13 checks on Movie Scene Map, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.