Skip to content

Ultimaps MCP server

com.ultimaps/mcpultimaps.comstreamable-httpv0.2.1Scanned

Create choropleth, category and pin maps of countries, states, counties and ZIP codes as images.

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Ultimaps MCP server can do

The Ultimaps MCP server is published by ultimaps.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: render_map), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (render_map).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • render_mapDraws a map of real places as an image: countries, states, counties or ZIP codes colored by data (a choropleth or heat map) or by category, with a legend, a title and pins.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 3,183 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...published as an interactive, clickable map to embed on a website (free account)."

      What this check looks for
    Description, as the server wrote it
    Draws a map of real places as an image: countries, states, counties or ZIP codes colored by data (a choropleth or heat map) or by category, with a legend, a title and pins. Borders come from real geographic data, not from an image model, and region names are matched for you. It draws only real places, never fictional or invented ones. The map is returned as an image in the conversation. Maps cover the world, continents, countries, their states, provinces and counties, and US ZIP code areas. Color regions with ONE of these (choropleth and categories are mutually exclusive): - `choropleth`: a number per region, e.g. {"values": {"California": 39.5, "Texas": 30.5}}. Classes, breaks and palette are picked from the data unless you set them. Say what the numbers are with `kind` (and `midpoint` when they have a meaningful center, `unit` for a short label unit): that is what gets percents, currencies, years and diverging scales right. When the data does not cover every region of the map, add `noData: true` so the legend explains the uncolored ones. - `categories`: a label per region, e.g. {"values": {"France": "Euro", "Poland": "Złoty"}}. Colors are assigned automatically unless you set `colors`. - `regions`: explicit hex colors, e.g. {"Texas": "#1D4ED8"}. Also works on top of either mode as an override. Region keys can be names, ISO/FIPS-style codes or common aliases. Typos are auto-corrected, and every correction or unmatched key is reported with suggestions, so there is no need to call get_map_regions first. Get `mapId` from list_maps if you don't know it. Also available: pins (`locations` with lat/lon), `title`, `legend` (position, `title`, `subtitle`), `style` (theme, borders, region labels; `style.labels.content: "value"` prints each region's value instead of its name and `"name_value"` stacks the name above the value, both needing `choropleth` or `categories`; `style.labels.fit` (default "auto") shortens labels that don't fit or overlap and never hides one; any still overlapping are reported in a `labels_overlap` warning with their keys), extra `layers`, and `output` size. A data legend needs a `legend.title`: what is measured, its unit and the year ("Median household income (US$, 2023)"). An untitled legend leaves the reader guessing. Short units ("%", "°C", "t") go in `choropleth.unit`, long ones ("litres per person") in the legend title. `dryRun: true` validates and previews region matching and the color plan without rendering. Without an API key: 30 renders per hour and 5 per minute per conversation (dry runs count), PNG up to 1600 px wide, with Ultimaps attribution on the image. The default 1200 px width is right for viewing in chat, and larger images are returned only as a link. Formats: png. SVG and PDF export are in Ultimaps Studio, from the edit link in the result. Every result includes an image link that works for 30 days, for chat apps that do not display images returned by tools. The result reports corrections, warnings, the resolved color plan, and an edit link that opens the map in Ultimaps Studio, where it can be edited, exported, or published as an interactive, clickable map to embed on a website (free account).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • title: Render map
Only reads 2Show 2 read-only tools
  • get_map_regionsLook up one map: title, regionType, regionCount, labels, layers, and its regions as {key, title}, 200 per page.No findings

    Why it is in this group

    • The name "get_map_regions" says "get": a word for reading.
    Description, as the server wrote it
    Look up one map: title, regionType, regionCount, labels, layers, and its regions as {key, title}, 200 per page. You rarely need this before rendering. render_map accepts region names, codes and common aliases and auto-corrects typos, reporting what it matched. Use it to build a dataset covering every region of a map, to see how a map names its regions, or to resolve a key render_map could not match. `query` searches keys, titles and aliases, so no hits means the map really has no such region. Use `offset` for further pages.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get map regions
  • list_mapsList the maps Ultimaps can render: the world, continents, countries subdivided into states, provinces, counties or departments, and US ZIP code areas.No findings

    Why it is in this group

    • The name "list_maps" says "list": a word for reading.
    Description, as the server wrote it
    List the maps Ultimaps can render: the world, continents, countries subdivided into states, provinces, counties or departments, and US ZIP code areas. Each row is {id, title, regionType, layers, regionCount, labels}. `id` is the mapId for render_map and get_map_regions; it is the map's slug on ultimaps.com (the last path segment, not the whole URL) and always means the current edition. `regionCount` is how many region keys a complete dataset needs. `labels: false` means the map has no region labels, so `style.labels` does nothing there. `layers` are the ids render_map's `layers` can turn on. Pass `query` to search ids, titles, region types and categories (e.g. "counties", "germany", "africa"). Only call this when you don't know the id: common ids such as `world`, `united-states` and `europe` just work, and an unknown id usually comes back with the closest ids.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List maps

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.ultimaps.com/mcp: tools/list returned 3 tools to an anonymous client, including render_map (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 3,183 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...published as an interactive, clickable map to embed on a website (free account)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff

Install

Pinned to version 0.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http ultimaps https://api.ultimaps.com/mcp
claude mcp add --transport http ultimaps https://api.ultimaps.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ultimaps__list_maps",
      "mcp__ultimaps__get_map_regions"
    ],
    "ask": [
      "mcp__ultimaps__render_map"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ultimaps. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ultimaps__render_map untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.ultimaps/mcp/verify?hash=5652cdeb04dbd83e472ecfeb7fc83000d4c87e61e60179eca18b358fe124ec71" | jq -e '.changed == false'

Pinned hash 5652cdeb04db, from Nov 8, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.ultimaps/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.ultimaps/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ultimaps/mcp.svg)](https://radar.anlyon.com/servers/com.ultimaps/mcp)

Source: MCP Registry · repository. Synced Nov 8, 2026, 15:17 UTC.

Ultimaps MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Ultimaps MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Ultimaps MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Ultimaps MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Ultimaps MCP server have?

3 tools: 1 write, 2 read. render_map, list_maps and get_map_regions.

Does the Ultimaps MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Ultimaps MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Ultimaps MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.