Moving Polygons
REMOTE · WWW.MOVINGPOLYGONS.COM
Create, edit and publish animated historical maps in your Moving Polygons account.
Available components
Last scanned (21 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Maps and Location
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1256 tokens (~83/item across 15 items; 14 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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
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.
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “finish_map_upload”, which the server declares destructive security
- Schema quality: 941 → 1256 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “start_map_upload” functional
- New tool “upload_map_part” functional
- 23 Oct 26 80
First indexed and scored.
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 24 Oct 2026 · Probed https://www.movingpolygons.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.movingpolygons.com | CN=YR1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 6a5595ded634db6da8a5d1b2198da7e4e14 |
| SANs: *.movingpolygons.com, movingpolygons.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.movingpolygons.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| movingpolygons.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Sign in to Moving Polygons to use this tool", resource_metadata="https://www.movingpolygons.com/.well-known/oauth-protected-resource/mcp", scope="profile email"
Bearer error="invalid_token", error_description="Sign in to Moving Polygons to use this tool", resource_metadata="https://www.movingpolygons.com/.well-known/oauth-protected-resource/mcp", scope="profile email"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://www.movingpolygons.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.movingpolygons.com/mcp |
| Authorisation server | https://clerk.movingpolygons.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.movingpolygons.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.movingpolygons.com/mcp | HTTPS enforced | 308 | https://www.movingpolygons.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 →
create_map Create a map ~49
Create a new private draft map from an import JSON of up to about 1 MB.
| Name | Type | Req | Description |
|---|---|---|---|
| map | – | yes | The map in the Moving Polygons import format, as a JSON object or a JSON string |
No output schema declared.
No examples provided.
create_upload_link Create an upload link ~94
A one-off link (valid 15 minutes) for uploading a map JSON file of up to 40 MB with curl. It creates a new draft map, or with mode replace overwrites an existing map's content. The curl output reports the result.
| Name | Type | Req | Description |
|---|---|---|---|
| mapId | string | – | Required for mode replace |
| mode | string | – | create (default): a new map. replace: overwrite mapId's content |
No output schema declared.
No examples provided.
finish_map_upload Finish a chunked map upload ~73
Joins parts 1 to the given count of a chunked upload, validates the map and creates the draft map (or replaces the map's content, keeping a backup). Reports missing parts or where the JSON breaks.
| Name | Type | Req | Description |
|---|---|---|---|
| parts | integer | yes | How many parts were sent |
| uploadId | string | yes | – |
No output schema declared.
No examples provided.
get_account Get account ~25
The signed-in user's public handle, plan and how many maps they can still create.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_import_format Get the map import format ~28
The JSON format for maps: layers with timed polygon keyframes, point markers and a style.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_map Get a map ~55
A summary of one of the user's maps (layers, keyframe dates, markers) and a 15-minute download link for its full import JSON, which can be several MB.
| Name | Type | Req | Description |
|---|---|---|---|
| mapId | string | yes | The map id |
No output schema declared.
No examples provided.
get_public_map Get a published map ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | – |
| url | string | – | e.g. https://www.movingpolygons.com/map/Chris/the-ottoman-empire-12991923 |
| username | string | – | – |
No output schema declared.
No examples provided.
list_maps List my maps ~47
The user's maps, most recently changed first, with their ids and links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 50 |
| search | string | – | Only maps whose name contains this text |
No output schema declared.
No examples provided.
publish_map Publish a map ~40
Make one of the user's maps public at its /map/<handle>/<slug> link, where anyone can view it.
| Name | Type | Req | Description |
|---|---|---|---|
| mapId | string | yes | – |
No output schema declared.
No examples provided.
replace_map_content Replace a map's content ~89
Overwrite an existing map's layers, markers, name, description and casualty bar (and style, if given) with an import JSON of up to about 1 MB. The link and publish state stay; the old content is backed up.
| Name | Type | Req | Description |
|---|---|---|---|
| map | – | yes | The map in the Moving Polygons import format, as a JSON object or a JSON string |
| mapId | string | yes | – |
No output schema declared.
No examples provided.
search_maps Search published maps ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 10 |
| query | string | – | Words to match, e.g. 'Ottoman', 'Holy Roman Empire', 'Ukraine war' |
| year | integer | – | Only maps whose timeline includes this year; negative for BC (-44 = 44 BC) |
No output schema declared.
No examples provided.
start_map_upload Start a chunked map upload ~91
Opens an upload (valid 2 hours) for a map JSON text that is sent in numbered parts through tool calls rather than over the network. It creates a new draft map, or with mode replace overwrites an existing map's content.
| Name | Type | Req | Description |
|---|---|---|---|
| mapId | string | – | Required for mode replace |
| mode | string | – | create (default): a new map. replace: overwrite mapId's content |
No output schema declared.
No examples provided.
unpublish_map Unpublish a map ~32
Make one of the user's maps private again (its public link stops working).
| Name | Type | Req | Description |
|---|---|---|---|
| mapId | string | yes | – |
No output schema declared.
No examples provided.
upload_map_part Upload one part of a map ~89
Stores one numbered piece of a chunked map upload. The pieces are joined in part order with nothing in between; sending a part number again replaces that part. Returns the piece's length and SHA-256.
| Name | Type | Req | Description |
|---|---|---|---|
| part | integer | yes | 1 for the first piece |
| text | string | yes | This piece of the map JSON text, verbatim |
| uploadId | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Moving Polygons MCP server?
Moving Polygons is a hosted endpoint at https://www.movingpolygons.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 · www.movingpolygons.com
claude mcp add --transport http com-movingpolygons-maps 'https://www.movingpolygons.com/mcp'
What is the Moving Polygons MCP server?
Moving Polygons is an MCP server listed in the public MCP registry as com.movingpolygons/maps. Create, edit and publish animated historical maps in your Moving Polygons account. This page covers its hosted endpoint (https://www.movingpolygons.com/mcp).
Is the Moving Polygons MCP server safe to use?
Moving Polygons scores 81 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 Moving Polygons MCP server expose?
Moving Polygons exposes 14 tools: get_import_format, get_account, list_maps, get_map, create_map, and 9 more. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.
Does the Moving Polygons MCP server require authentication?
Yes. Moving Polygons asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Moving Polygons MCP server still maintained?
Moving Polygons is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.