moving-polygons
https://www.movingpolygons.com
Registry code: 2d4ff913a41801c7
Moving Polygons (movingpolygons.com) turns timed polygons into animated maps: borders that morph between keyframes, plus point markers. Most tools act on the user's own account; the first call to one of them asks the user to sign in. search_maps, get_public_map and get_import_format work without signing in.
Workflow for a new map:
- endpoint
- https://www.movingpolygons.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 moving-polygons live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is moving-polygons free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does moving-polygons have?
- 11 tools: get_public_map, publish_map, create_upload_link, replace_map_content, get_map, create_map, get_account, list_maps, ….
- Is moving-polygons 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 11 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.
publish_map auth-required never probed
Make one of the user's maps public at its /map/<handle>/<slug> link. Only call this when the user explicitly asked to publish.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mapId" ], "properties": { "mapId": { "type": "string" } } }arguments 12 linescreate_upload_link auth-required never probed
A one-off link (valid 15 minutes) to upload a map JSON file with curl: creates a new draft map, or (mode replace) replaces an existing map's content. Use this for maps over ~1 MB or files on disk. The curl output reports the result.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "mode": { "enum": [ "create", "replace" ], "type": "string", "description": "create (default): a new map. replace: overwrite mapId's content" }, "mapId": { "type": "string", "description": "Required for mode replace" } } }arguments 18 linesreplace_map_content auth-required never probed
Overwrite an existing map's layers, markers, name, description and casualty bar (and style, if given) with an import JSON (up to ~1 MB; else create_upload_link with mode replace). The link and publish state stay; the old content is backed up.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mapId", "map" ], "properties": { "map": { "anyOf": [ { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {} }, { "type": "string" } ], "description": "The map in the import format (see get_import_format), as a JSON object or a JSON string" }, "mapId": { "type": "string" } } }arguments 28 linesget_map auth-required never probed
A summary of one of the user's maps (layers, keyframe dates, markers) and a download link for its full import JSON (fetch it with curl; it can be several MB).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mapId" ], "properties": { "mapId": { "type": "string", "description": "The map id (from list_maps)" } } }arguments 13 linescreate_map auth-required never probed
Create a new private draft map from an import JSON (up to ~1 MB). For bigger maps or files on disk use create_upload_link instead.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "map" ], "properties": { "map": { "anyOf": [ { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {} }, { "type": "string" } ], "description": "The map in the import format (see get_import_format), as a JSON object or a JSON string" } } }arguments 24 linesget_account auth-required 1h ago
The signed-in user's public handle, plan and how many maps they can still create.
{ "type": "object", "properties": {} }arguments 4 lineslist_maps auth-required 1h ago
The user's maps, most recently changed first, with their ids and links.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Default 50" }, "search": { "type": "string", "description": "Only maps whose name contains this text" } } }arguments 16 linessearch_maps auth-required never probed
Find published animated maps on Moving Polygons (history, wars, empires, borders, epidemics, sea ice…) by words in their title or description and/or a year they cover. Returns links to the interactive map, its text version and its article.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "year": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "Only maps whose timeline includes this year; negative for BC (-44 = 44 BC)" }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Default 10" }, "query": { "type": "string", "description": "Words to match, e.g. 'Ottoman', 'Holy Roman Empire', 'Ukraine war'" } } }arguments 22 linesunpublish_map auth-required never probed
Make one of the user's maps private again (its public link stops working).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mapId" ], "properties": { "mapId": { "type": "string" } } }arguments 12 linesget_import_format auth-required never probed
The JSON format for maps (layers with timed polygon keyframes, markers, style). Read it before building a map.
{ "type": "object", "properties": {} }arguments 4 linesget_public_map unknown 1h ago
One published map as Markdown: description and sources, the timeline of keyframes (date and caption), layers, events, and the iframe code to embed the interactive map. Pass its URL, or the handle and slug.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "url": { "type": "string", "description": "e.g. https://www.movingpolygons.com/map/Chris/the-ottoman-empire-12991923" }, "slug": { "type": "string" }, "username": { "type": "string" } } }arguments 16 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 id2d4ff913a41801c7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d4ff913a41801c7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2d4ff913a41801c7?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.