moviescenemap
Registry code: 61f97c38986f4f2d
Read-only tools over Movie Scene Map: 37,184 real filming locations, plus 166 whole countries or regions that carry nothing but video-game settings, for 37,259 films, series and games across 181 countries. The backbone is "filming location" (P915) statements on Wikidata joined to each place's coordinates and Wikipedia article; some records additionally carry places named in the production's own English Wikipedia article, ALWAYS in fields prefixed wiki_ and never merged with the statements — quote those as "per Wikipedia". Nothing is scraped from listicles and nothing is generated. TWO RULES…
- endpoint
- https://moviescenemap.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is moviescenemap live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is moviescenemap free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does moviescenemap have?
- 8 tools: where_was_it_filmed, search_locations, search_productions, what_was_filmed_here, locations_near, top_locations, get_statistics, list_countries.
- Is moviescenemap safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
top_locations open 1h ago
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>".
{ "type": "object", "properties": { "sort": { "enum": [ "fame", "productions" ], "type": "string", "description": "Ranking (default fame)" }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "How many (default 10)" }, "country": { "type": "string", "description": "Country name or ISO code (optional — omit for worldwide)" }, "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)" } } }arguments 27 linesget_statistics open 1h ago
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.
{ "type": "object", "properties": {} }arguments 4 lineslist_countries open 1h ago
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.
{ "type": "object", "properties": {} }arguments 4 lineswhere_was_it_filmed unknown never probed
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 37,259 productions across 37,350 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.
{ "type": "object", "required": [ "title" ], "properties": { "limit": { "type": "integer", "maximum": 200, "minimum": 1, "description": "Max places (default 50)" }, "title": { "type": "string", "description": "Title, or its slug, e.g. \"Skyfall\", \"game-of-thrones\", \"The Third Man\"" } } }arguments 18 linessearch_locations unknown never probed
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.
{ "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)" } } }arguments 26 linessearch_productions unknown never probed
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.
{ "type": "object", "required": [ "query" ], "properties": { "kind": { "enum": [ "film", "tv", "game", "anime", "manga" ], "type": "string", "description": "Restrict to one medium (optional)" }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 10)" }, "query": { "type": "string", "description": "Title or part of one, e.g. \"bond\", \"star wars\"" } } }arguments 29 lineswhat_was_filmed_here unknown never probed
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.
{ "type": "object", "required": [ "place" ], "properties": { "limit": { "type": "integer", "maximum": 200, "minimum": 1, "description": "Max productions (default 50)" }, "place": { "type": "string", "description": "Place slug (preferred) or name, e.g. \"durham-cathedral\"" } } }arguments 18 lineslocations_near unknown never probed
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.
{ "type": "object", "required": [ "latitude", "longitude" ], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 15)" }, "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)" }, "latitude": { "type": "number", "maximum": 90, "minimum": -90 }, "longitude": { "type": "number", "maximum": 180, "minimum": -180 }, "radius_km": { "type": "number", "maximum": 500, "minimum": 1, "description": "Search radius in km (default 50)" } } }arguments 35 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id61f97c38986f4f2d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/61f97c38986f4f2d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/61f97c38986f4f2d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.