Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Moving Polygons is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Create, edit and publish animated historical maps in your Moving Polygons account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moving-polygons-mcp https://www.movingpolygons.com/mcp
# 2 — ask your agent for something these tools do
# get_import_format, get_account, list_maps and 11 more
Moving Polygons costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http moving-polygons-mcp https://www.movingpolygons.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The JSON format for maps: layers with timed polygon keyframes, point markers and a style.
No parameter schema on file.
The signed-in user's public handle, plan and how many maps they can still create.
No parameter schema on file.
The user's maps, most recently changed first, with their ids and links.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only maps whose name contains this text |
| limit | integer | no | Default 50 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapId | string | yes | The map id |
Create a new private draft map from an import JSON of up to about 1 MB.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| map | yes | The map in the Moving Polygons import format, as a JSON object or a JSON string |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | create (default): a new map. replace: overwrite mapId's content |
| mapId | string | no | Required for mode replace |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | create (default): a new map. replace: overwrite mapId's content |
| mapId | string | no | Required for mode replace |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uploadId | string | yes | — |
| part | integer | yes | 1 for the first piece |
| text | string | yes | This piece of the map JSON text, verbatim |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uploadId | string | yes | — |
| parts | integer | yes | How many parts were sent |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapId | string | yes | — |
| map | yes | The map in the Moving Polygons import format, as a JSON object or a JSON string |
Make one of the user's maps public at its /map/<handle>/<slug> link, where anyone can view it. The user must first choose a username at https://www.movingpolygons.com/settings; until then this fails and says so.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapId | string | yes | — |
Make one of the user's maps private again (its public link stops working).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapId | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to match, e.g. 'Ottoman', 'Holy Roman Empire', 'Ukraine war' |
| year | integer | no | Only maps whose timeline includes this year; negative for BC (-44 = 44 BC) |
| limit | integer | no | Default 10 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | e.g. https://www.movingpolygons.com/map/chrisjager/the-ottoman-empire-12991923 |
| username | string | no | The map owner's handle, e.g. chrisjager (with slug, instead of url) |
| slug | string | no | The last part of the map's URL, e.g. the-ottoman-empire-12991923 |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Moving Polygons or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_import_format | no tags | |
| get_account | no tags | |
| list_maps | no tags | |
| get_map | untrusted-input | untrusted-input: keyword "download" |
| create_map | state-write | state-write: declares readOnlyHint: false |
| create_upload_link | external-sink | external-sink: keyword "curl" |
| start_map_upload | state-write | state-write: declares readOnlyHint: false |
| upload_map_part | state-write | state-write: declares readOnlyHint: false |
| finish_map_upload | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| replace_map_content | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| publish_map | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| unpublish_map | state-write | state-write: declares readOnlyHint: false |
| search_maps | no tags | |
| get_public_map | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Moving Polygons can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.