Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ShowMeOnMap

REMOTE · SHOWMEONMAP.COM · 2 COMPONENTS

Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools.

0 this week 93 Trust /100

Last scanned (4 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability74
  • 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
  • Context-footprint check failed: tool/resource definitions use about 7840 tokens (~230/item across 34 items; 32 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 68% 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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 34 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
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 5 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “analyze” functional
  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “build_map” rewrote its description, which is the text the model reads security
    • New tool “osm_features” functional
  • 3 Nov 26 0
    • “run_analysis” added an optional parameter “radiusKm” cosmetic
    • “run_analysis” added an optional parameter “overlapLayerId” cosmetic
    • “run_analysis” added an optional parameter “withinLayerId” cosmetic
    • “run_analysis” reworded the description of “analysis” cosmetic
    • “run_analysis” reworded the description of “sumFields” cosmetic
    • “run_analysis” reworded the description of “valueField” cosmetic

    6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 27 Oct 26 +1
    • Judged manipulation: unverified → pass ▲ security
    • Tool “build_map” rewrote its description, which is the text the model reads security
    • “build_map” added an optional parameter “resume_token” cosmetic
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 0
    • Stability: pass → 0.97 functional
  • 10 Oct 26 0
    • Judged manipulation: pass → unverified ▼ security
    • DNSSEC: fail → pass ▲ security
    • First check of Capabilities: pass functional
  • 30 Sept 26 0
    • Schema quality: excellent → good functional
    • “add_annotation” reworded the description of “rationale” cosmetic
    • “export_workspace” reworded the description of “rationale” cosmetic
    • “filter_layer” reworded the description of “rationale” cosmetic
    • “focus_area” reworded the description of “rationale” cosmetic
    • “get_state” reworded the description of “rationale” cosmetic
    • “list_workflows” reworded the description of “rationale” cosmetic
    • “mutate_map” reworded the description of “rationale” cosmetic
    • “query_features” reworded the description of “rationale” cosmetic
    • “redo” reworded the description of “rationale” cosmetic
    • “remove_annotation” reworded the description of “rationale” cosmetic
    • “remove_layer” reworded the description of “rationale” cosmetic
    • “rename_layer” reworded the description of “rationale” cosmetic
    • “report_blocker” reworded the description of “rationale” cosmetic
    • “restyle_layer” reworded the description of “rationale” cosmetic
    • “run_analysis” reworded the description of “rationale” cosmetic
    • “run_workflow” reworded the description of “rationale” cosmetic
    • “save_workflow” reworded the description of “rationale” cosmetic
    • “select_within” reworded the description of “rationale” cosmetic
    • “set_camera” reworded the description of “rationale” cosmetic
    • “set_time” reworded the description of “rationale” cosmetic
    • “tag” reworded the description of “rationale” cosmetic
    • “undo” reworded the description of “rationale” cosmetic
    • “export_image” reworded the description of “rationale” cosmetic
    • “correlate_layers” reworded the description of “rationale” cosmetic
    • “clear_filters” reworded the description of “rationale” cosmetic
    • “build_map” reworded the description of “rationale” cosmetic
    • “add_layer” reworded the description of “rationale” cosmetic
    • “add_fusion_layer” reworded the description of “rationale” cosmetic
    • “export_layer_data” reworded the description of “rationale” cosmetic
    • “filter_layer” made “rationale” optional cosmetic
    • “focus_area” made “rationale” optional cosmetic
    • “get_state” made “rationale” optional cosmetic
    • “list_workflows” made “rationale” optional cosmetic
    • “mutate_map” made “rationale” optional cosmetic
    • “query_features” made “rationale” optional cosmetic
    • “redo” made “rationale” optional cosmetic
    • “remove_annotation” made “rationale” optional cosmetic
    • “remove_layer” made “rationale” optional cosmetic
    • “rename_layer” made “rationale” optional cosmetic
    • “report_blocker” made “rationale” optional cosmetic
    • “restyle_layer” made “rationale” optional cosmetic
    • “run_analysis” made “rationale” optional cosmetic
    • “run_workflow” made “rationale” optional cosmetic
    • “save_workflow” made “rationale” optional cosmetic
    • “select_within” made “rationale” optional cosmetic
    • “set_camera” made “rationale” optional cosmetic
    • “set_time” made “rationale” optional cosmetic
    • “tag” made “rationale” optional cosmetic
    • “undo” made “rationale” optional cosmetic
    • “export_layer_data” made “rationale” optional cosmetic
    • “export_image” made “rationale” optional cosmetic
    • “correlate_layers” made “rationale” optional cosmetic
    • “clear_filters” made “rationale” optional cosmetic
    • “build_map” made “rationale” optional cosmetic
    • “add_layer” made “rationale” optional cosmetic
    • “add_fusion_layer” made “rationale” optional cosmetic
    • “export_workspace” made “rationale” optional cosmetic
    • “add_annotation” made “rationale” optional cosmetic
Diagnostics

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 5 Nov 2026 · Probed https://showmeonmap.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=showmeonmap.com CN=WE1,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 408dda7a81e5f64f0eb3ad1c901f1904
SANs: showmeonmap.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of showmeonmap.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
showmeonmap.com. present 2371 13 Verified
showmeonmap.com. Verified address RRset verified with the apex keys
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 resource_metadata="https://showmeonmap.com/.well-known/oauth-protected-resource/api/mcp", scope="mcp"

Bearer resource_metadata="https://showmeonmap.com/.well-known/oauth-protected-resource/api/mcp", scope="mcp"
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' blob: https://static.cloudflareinsights.com; object-src 'none'; base-uri 'self'; form-action 'self'; style-src 'self' 'unsafe-inline'; worker-src 'self' blob:; child-src blob:; img-src 'self' data: blob: https:; font-src 'self' data:; frame-src https://www.youtube-nocookie.com; connect-src 'self' https://cloudflareinsights.com https://api.maptiler.com https://*.tile.thunderforest.com https://basemaps.cartocdn.com https://*.basemaps.cartocdn.com https://basemapstyles-api.arcgis.com https://ibasemaps-api.arcgis.com https://geocode-api.arcgis.com https://tile.googleapis.com https://tiles.maps.eox.at blob: https://fonts.openmaptiles.org https://openmaptiles.github.io https://tiles.openfreemap.org https://openfreemap.org https://s3.amazonaws.com https://*.s3.amazonaws.com https://*.s3.us-west-2.amazonaws.com https://api.protomaps.com https://gibs.earthdata.nasa.gov https://nsidc.org https://droughtmonitor.unl.edu https://www.nhc.noaa.gov http
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Protected resource metadata

Document https://showmeonmap.com/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://showmeonmap.com/api/mcp
Authorisation server https://showmeonmap.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://showmeonmap.com/api/mcp Verified 200
http (plaintext) http://showmeonmap.com/api/mcp HTTPS enforced 301 https://showmeonmap.com/api/mcp
MCP tools · 32 exposed · ~7,424 tokens

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 →

Tool Tokens
add_annotation ~165

Add a user-placed label at a specific coordinate. Annotations are independent of layers and live in their own id namespace. Strict: the id must not already be in use by another CURRENTLY-placed annotation (removed ids can be recycled).

NameTypeReqDescription
colorstring–Optional CSS color for the marker + label.
coordsarrayyes[lng, lat] in WGS84.
idstringyesStable id for this annotation — caller-supplied.
labelstring–Optional text rendered at the point.
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

add_fusion_layer ~201

Spatially join two existing layers and add a new layer that encodes both values per region as a 3x3 bivariate choropleth. Both layers must already exist in the workspace. Auto-detects the numeric value field from each layer's viz config; pass value_field_a / value_field_b to override. Returns the new layer_id, correlation r, and matched-feature count. Required: map_id, layer_a_id, layer_b_id.

NameTypeReqDescription
layer_a_idstringyes–
layer_b_idstringyes–
map_idstringyes–
modestring––
new_layer_idstring––
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
value_field_astring––
value_field_bstring––

No output schema declared.

No examples provided.

add_layer ~258

Append a fully-constructed LayerPlan to an existing workspace without going through NL. Pass the same shape the workspace pipeline emits — { id, title, source, viz, geometry, ... }. Takes a structured plan; natural-language edits go through mutate_map. The full LayerPlan and Op spec are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.

NameTypeReqDescription
intentstring–Optional. Which mental model is this add_layer operating under? "primary-data" = the layer the user actually asked to see; "context-overlay" = supporting data layered on top of a primary; "reference-…
layerPlanobjectyesFull LayerPlan object. Must include id, title, source, viz, geometry.
map_idstringyesmap_id from a prior build_map call
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

analyze ~395

One call for a question that combines datasets: "which Asian capitals had the most earthquakes within 300 km this month", "people within 30 km of each volcano in Indonesia", "how much of each African country is desert". Give a plan: acquire steps (ask = a dataset in plain words answered without a model; hazard = USGS / GVP / FIRMS / GDACS; osm = exact OSM tags in an area), then op steps (within, overlap, zonal, join, population, near, rank, filter) that name their inputs by step id. The code computes, no model: returns a shareable map, a table of the answer step (top rows), a ledger naming each number's source and op, and a grounded summary. A step that cannot run fails the whole plan with that step named and why (a source that did not answer is never reported as "none"). Costs 1 credit; refunded when it fails or the answer is empty. Use build_map for a single dataset.

NameTypeReqDescription
map_idstring–Optional: run on this map — acquire {layer} reads its layers, and the result is added to it instead of a new map
planobjectyesAcquire datasets, then compute over them. Example: [{id:"capitals",acquire:{ask:"capitals of Asia"}},{id:"quakes",acquire:{hazard:"earthquakes",place:"Asia",days:30}},{id:"x",op:"within",target:"capi…
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

build_map ~424

Make an interactive, data-driven map from a plain-language request, built from live public data with every value cited to its source. Covers natural hazards (earthquakes, wildfires, volcanoes, tropical storms, floods), weather and air quality, statistics by country, state or region (GDP, population, health, emissions — World Bank, Eurostat, US Census), infrastructure and transit (railways, power plants, transit lines, roads), parks and terrain, and points of interest from OpenStreetMap. The query carries the place, time window and any thresholds — "earthquakes above magnitude 5 near Japan this month", "GDP per capita across Europe" — and the server applies them itself. Returns a shareable link and a map_id for follow-ups (mutate_map, filter_layer, get_state); in clients that support MCP Apps the map also renders interactively in the conversation. Analysis maps (site selection, spatial analysis) can take one to three minutes: when the build outlasts one call it returns status "building" with a resume_token, and calling build_map again with the same query and that resume_token collects the map without spending credits. A request already written as OpenStreetMap tags, a bounding box, or "everything within N m of a coordinate" maps exactly through osm_features, which takes the tags and the area as given. The Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.

NameTypeReqDescription
querystringyesNatural language: "coffee shops in Tokyo", "GDP by country", "volcanoes in Indonesia", etc.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
resume_tokenstring–Only when a previous build_map returned status "building": its resume_token, to collect that map. Collecting spends no credits.

No output schema declared.

No examples provided.

clear_filters ~154

Wipe every predicate currently applied to a layer's filter chain, making every source feature visible again. Inverse of filter_layer. No-op on layers that have no existing filter. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

NameTypeReqDescription
confirmedboolean–Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. A cleared filter chain can be restored with undo.
layerIdstringyes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

correlate_layers ~171

Spatially join two existing workspace layers and return the Pearson correlation coefficient r, sample size n, two-sided p-value approximation, plus human-readable strength and direction labels. Pure read — no layer is added, no op is committed, no credit charge. Returns numbers only; add_fusion_layer renders the same join as a map layer. Required: map_id, layer_a_id, layer_b_id.

NameTypeReqDescription
layer_a_idstringyes–
layer_b_idstringyes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
value_field_astring––
value_field_bstring––

No output schema declared.

No examples provided.

export_image ~150

Returns a deep-link URL that opens the map in the user's browser and automatically triggers a PNG download. The user clicks the link, the browser renders the map at full resolution with the legend composited (if legend: true), and the file downloads. There is no server-side rendering; the user's browser is the renderer. Required: map_id. Optional: format (png default), legend (true default).

NameTypeReqDescription
formatstring––
legendboolean––
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

export_layer_data ~156

Export a single layer's features as a downloadable file. Returns a URL with Content-Disposition: attachment so the user's browser downloads it. CSV drops geometry beyond a (lng, lat) centroid — for full polygon/line geometry, use format: "geojson". The URL is an unguessable capability link that does NOT expire: anyone with the link can download the file. Required: map_id, layer_id, format.

NameTypeReqDescription
formatstringyes–
layer_idstringyes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

export_workspace ~122

Return the current workspace document (ops log + cursor + meta) plus the materialized mapPlan and layerFilters, in a shape suitable for save-to-file / share-by-URL / inspection. Pure read — no mutation, no credit charge. This is the full raw state for serialization; get_state returns a compact summary for display.

NameTypeReqDescription
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

filter_layer ~284

Narrow a layer to features matching a structured predicate. `append:true` (default) conjoins with any existing filter; `append:false` replaces the chain.

NameTypeReqDescription
appendboolean–Default true. false replaces the layer's existing filter chain.
intentstring–Optional. Which mental model is this filter operating under? "narrow" = generic shrink-the-set; "isolate-outliers" = pull out anomalies for inspection; "compare-subset" = pre-step before a side-by-si…
layerIdstringyesid of the layer to filter
map_idstringyes–
predicateobjectyesPredicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",chil…
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

focus_area ~214

Refine an existing layer to a NAMED area the server resolves from OpenStreetMap — a street corridor ("Broadway from Arbutus Street to Main Street"), a place ("Mount Pleasant"), or an intersection surroundings. Pass names only, never coordinates; unresolvable names return a clarification with real nearby candidates instead of guessed geometry. Emits ordinary undoable ops (filter / new layer + camera) and a grounded summary like "kept 37 of 150 features". Costs 1 credit when a mutation lands; clarifications are refunded.

NameTypeReqDescription
areaRef–yes–
layerIdstringyes–
map_idstringyes–
modestring–filter (default): hide features outside, reversible. select: copy matches into a new layer. clip: new layer with geometry trimmed at the boundary.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

get_map_view ~60

Used by the ShowMeOnMap map card to load a map version. Not for the model.

NameTypeReqDescription
cursorinteger––
layer_idsarray––
map_idstringyes–
op_idstring––

No output schema declared.

No examples provided.

get_state ~72

Return the current workspace, map plan, and active filters for a given map_id.

NameTypeReqDescription
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

list_workflows ~63

List the caller's saved workflows with their parameters and per-run credit estimates.

NameTypeReqDescription
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

mutate_map ~170

Apply a natural-language instruction to an existing workspace. Valid mutations: filter a layer, remove a layer, change camera, change basemap. For ambiguous instructions the tool emits a clarification field. For unrelated instructions it emits outOfScope — build a new map in that case. The full Op catalog and predicate grammar are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.

NameTypeReqDescription
instructionstringyese.g., "filter to where magnitude is greater than 5", "change basemap to dark"
map_idstringyesmap_id from a prior build_map call
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

osm_features ~303

Map and list OpenStreetMap objects matching exact OSM tags inside an area — a bbox, a point and radius, or a named place. Use when you know the tags ("place=village|hamlet", "amenity=clinic", "railway=tram", "highway=*+name=Rue de Lyon") or need everything near a coordinate with distances; use build_map for natural-language questions and statistics. No model interpretation: tags and area are taken as given, every feature is an OSM object with all its tags. Each layer reports ok / empty (OSM has none matching here) / unavailable (no source answered — says nothing about whether any exist). Returns a shareable map plus a compact table per layer (name, osm id, distance_m for point searches, address, coordinates). Costs 1 credit; refunded when no layer has a feature.

NameTypeReqDescription
areaobjectyesExactly one of: bbox, point + radius_m, or place (its extent; add radius_m for a radius around it, e.g. an address). Areas up to ~300 km across.
layersarrayyes1–5 layers, each drawn and listed separately
limitinteger–Max features per layer (default 200)
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

query_features ~233

Evaluate a predicate against a layer's inline features and return the matching subset. No Op is emitted and the workspace is not mutated. Handy for introspection ("how many X match Y?") before deciding whether to filter, subset, or build a new layer.

NameTypeReqDescription
layerIdstringyes–
limitinteger–Default 100, max 1000. Response sets `truncated:true` when clipped.
map_idstringyes–
predicateobjectyesPredicate in the Mongo-shape grammar. Examples: {op:"eq",field:"category",value:"cafe"}, {op:"gt",field:"magnitude",value:5}, {op:"within",geometry:{type:"Polygon",coordinates:[...]}}, {op:"and",chil…
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

redo ~129

Advance the workspace cursor by one toward the tail of the ops log, replaying the next op that was previously undone. Calling redo when the cursor is already at the tail (no undone ops to fast-forward) fails rather than silently no-op. Note: any new op applied via apply-op / mutate-map after an undo truncates the redo tail (standard edit-stack semantics).

NameTypeReqDescription
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

remove_annotation ~115

Drop a previously-placed annotation by id. Strict: removing an already-removed or never-placed id fails. After removal, the id CAN be re-used by a later add_annotation (unlike layer ids, which are tombstoned for the session).

NameTypeReqDescription
annotationIdstringyes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

remove_layer ~176

Drop a layer from the workspace by id. Strict: removing an already-removed or never-added layer fails. Layer ids do NOT recycle — a removed id cannot be re-added later in the same workspace. GATED: this tool is destructive. Pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

NameTypeReqDescription
confirmedboolean–Set to true to confirm this destructive action. If omitted or false, the call returns a needs_confirmation envelope. Layer ids are tombstoned — once removed, the same id cannot be re-added later in t…
layerIdstringyes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

rename_layer ~145

Change a layer's id from oldLayerId to newLayerId. Re-keys any existing filter chain and preserves insertion order among sibling layers. Strict: newLayerId must not already be in use (current OR tombstoned) in this workspace. Subsequent ops must reference the layer by its new id.

NameTypeReqDescription
map_idstringyes–
newLayerIdstringyesNew id. Must be unique within the workspace.
oldLayerIdstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

report_blocker ~270

Send the ShowMeOnMap team a report about a request this server could not complete — an unsupported intent, a missing tool, an unclear schema, or an op that failed in a confusing way. Records the report to a server-side log for future capability work; it does not change the current map or session. map_id is optional, so a report can be filed before any map exists.

NameTypeReqDescription
map_idstring–Optional. The map_id you were working on, if any.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
suggested_capabilitystring–Optional. A new tool, op, or schema field that would have unblocked you.
what_i_triedstringyesWhich tools / inputs you attempted, in order. Be specific — tool name + key arg shape is ideal.
what_i_was_tryingstringyesHigh-level intent in one or two sentences. e.g. "merge two filtered choropleths into a fused bivariate map".
where_i_got_stuckstringyesThe specific failure: what came back, what was missing, why you could not proceed.

No output schema declared.

No examples provided.

restyle_layer ~150

Adjust a layer's color and/or opacity. Within-palette changes only — the renderer silently ignores fields the current viz variant doesn't support. Pass at least one of color / opacity; passing neither is an accepted no-op.

NameTypeReqDescription
colorstring–CSS color string: hex (#RRGGBB), rgb/rgba, or named color.
layerIdstringyes–
map_idstringyes–
opacitynumber–0 (transparent) to 1 (opaque).
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

run_analysis ~1,606

Compute a spatial analysis server-side and append the finished, honestly-legended result as a new layer + camera; the result REPLACES its input layer(s) (undoable). hotspot = Getis-Ord Gi*: hot/cold significance classes (99/95/90%, Benjamini-Hochberg FDR-corrected) on a numeric field, or on hex-binned point density when valueField is omitted. zonal = aggregate points into polygon zones (an existing zone layer OR a generated h3 fishnet): count/sum/mean/min/max per zone as a quantile choropleth where zero and no-data are distinct classes. enrich = join a US Census ACS indicator (median income, home value, rent, …) onto each feature by tract/county/state containment — unmatched features stay null, never zero-filled. join = spatial join (attribute transfer): each point in layerId takes properties from the joinLayerId polygon containing it (collisions prefixed, unmatched points carry NO joined fields, zero overlap is a typed rejection). merge = append two same-geometry-class layers into one dataset with a per-row source column (schemas never null-filled; class mismatch is a typed failure). near = nearest-neighbor distance columns (great-circle meters, stated — never presented as road distance). dissolve = true polygon union per attribute group (missing values form their own group; partial sums reported). Returns a grounded memo + stats payload — every number is computed, never generated; findings keep the map. Costs 1 credit when the result lands; typed failures (unknown layer, too few features, >10,000-feature cap) are refunded.

NameTypeReqDescription
analysisstringyesWhich analysis to run. 'hotspot' = Getis-Ord Gi* with FDR-corrected significance classes. 'zonal' = aggregate a point layer into polygon zones (count/sum/mean/min/max choropleth). 'enrich' = join a U…
annotateboolean–Opt-in: place ONE callout annotation at the headline feature (hottest cluster / top zone / highest value). Label text comes only from computed values.
dissolveFieldstring–dissolve only: group-by property (omit = dissolve ALL into one footprint); missing values form their own "(no value)" group.
fieldsarray–join only: which join-layer properties to transfer (default: auto-select up to 12 non-internal properties, overflow reported).
geoLevelstring–enrich only: containment geography (default tract). Tract/county fetch only the states the data touches, capped at 3 — filter first or use state for wider layers.
hexMetersnumber–hotspot density mode only: hex cell spacing in meters (default auto from the data extent).
indicatorstring–enrich only (required there): a US Census ACS preset id (e.g. 'median_household_income', 'median_home_value', 'median_rent') or a raw ACS variable code (e.g. 'B19013_001E').
joinLayerIdstring–join only (required there): the POLYGON layer providing the attributes.
kinteger–hotspot only: nearest neighbors per feature (default 8).
layerIdstringyesThe workspace layer to analyze (geojson-backed; the point source for zonal; the point TARGET for join; the styling donor for merge).
map_idstringyes–
maxDistanceMnumber–near only: search radius in meters — a point whose nearest neighbor is farther carries NO near fields (reported).
mergeLayerIdstring–merge only (required there): the second layer — same geometry class (point/line/polygon) as layerId.
nearFieldstring–near only: property of the nearest feature to copy as its identity (default: first name-like property).
nearLayerIdstring–near only (required there): the POINT layer to search for each target point's nearest neighbor.
overlapLayerIdstring–overlap only (required there): the POLYGON layer whose area inside each target is measured.
prefixstring–join only: prefix for a joined field whose name collides with an existing target property (default "join_").
radiusKmnumber–within (required there): the radius in km (great-circle) to count within. population: the circle round each POINT (required for points).
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
sourceFieldstring–merge only: name of the per-row provenance column naming each row's source layer (default "merge_source"; renamed on collision, reported).
statsarray–zonal only: which statistics to attach per zone (default: count, plus sum/mean/min/max when valueField is set).
storyboolean–Opt-in: persist the shared map with a 2-step story rail (grounded overview + analysis memo isolating the result layer) — the /m/ link opens with it.
sumFieldsarray–dissolve: numeric properties to SUM per group — skipped values reported, a group with none present carries NO sum. overlap: numeric properties of overlapLayerId to apportion by area into each target.
valueFieldstring–Numeric property to analyze. hotspot: omit on point layers for incident-DENSITY mode (hex-binned counts). zonal: omit for count-only aggregation. within: a property of the withinLayerId points to sum…
withinLayerIdstring–within only (required there): the POINT layer to count around each target point.
zoneLayerIdstring–zonal only: an existing polygon layer to aggregate into. Provide EXACTLY ONE of zoneLayerId or zones.
zonesobject–zonal only: generate an h3 hex fishnet over the source extent instead of using a zone layer (resolution 3-10, default auto). Provide EXACTLY ONE of zoneLayerId or zones.

No output schema declared.

No examples provided.

run_workflow ~224

Execute a saved workflow with parameter values. PAID: bills ~1 credit per step through the normal build/mutate paths (the estimate is in list_workflows). Optional batch mode sweeps ONE param across 2–20 values — each value is a full independent run (steps × values credits); failed/paused values are reported per value and the batch continues. A clarification pauses a single run (status "paused" + the question); failures stop at the failing step. On success the result is a live map with a shareable URL (batch: the last successful value's map).

NameTypeReqDescription
batchobject–Batch mode: run the workflow once per value ("each of the 12 districts"). Bills steps × values.
paramsobject–Values for the workflow's declared parameters.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
workflow_idstringyesFrom save_workflow or list_workflows.

No output schema declared.

No examples provided.

save_workflow ~172

Save a re-runnable, parameterized workflow: an ordered list of natural-language instructions (step 1 builds, later steps mutate). Wrap values in {braces} and declare them in params. Running it later re-executes the instructions on FRESH data and bills per step like typing.

NameTypeReqDescription
namestringyesWorkflow name.
paramsarray–Declared parameters — every {slot} used in steps must be declared here.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
stepsarrayyesOrdered NL instructions. Step 1 builds the map; later steps mutate it. Wrap values in {braces} to declare parameters.

No output schema declared.

No examples provided.

select_within ~172

Create a new layer containing the source layer's features that lie within the supplied polygon. The source layer is untouched. Useful for "show me only the X inside this country/bbox/hand-drawn shape."

NameTypeReqDescription
inheritStyleboolean–Default true. false emits a new layer with minimal default styling.
map_idstringyes–
newLayerIdstringyesId for the new layer. Must not already be in use in this workspace.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
selectionobjectyesGeoJSON Polygon or MultiPolygon in [lng,lat] coordinate order.
sourceLayerIdstringyes–

No output schema declared.

No examples provided.

set_camera ~161

Override the workspace camera. Latest set_camera op wins during replay. Two modes: `fitBounds` with a [w,s,e,n] bbox (plus optional padding/animateMs), or `flyTo` with [lng,lat] center + zoom (plus optional pitch/bearing/animateMs). Covers requests like "zoom to Japan", "center on Paris at z=10", or framing a filtered layer. Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip.

NameTypeReqDescription
camera–yes–
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

set_time ~201

Override the current time-range filter. Latest set_time op wins during replay. Covers requests like "filter to 2020-2024" or "show only the last 7 days". Not yet consumed by the renderer — the UI drives the slider directly — but the value is captured in the ops log and queryable via get_state.

NameTypeReqDescription
fieldstringyesFeature property carrying the time value (e.g. "date", "year", "timestamp").
formatstring–How rangeStart/rangeEnd encode time. Default: unix_ms at render time.
map_idstringyes–
rangeEndnumberyesInclusive upper bound of the visible window.
rangeStartnumberyesInclusive lower bound of the visible window.
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

tag ~130

Label the current workspace state with a user-supplied name. The label is mirrored into workspace.meta.tags so UIs can render a named-revision history. Tagging the same label twice is idempotent — no error, no duplicate entry.

NameTypeReqDescription
map_idstringyes–
namestringyesCheckpoint label, e.g. "before EV layer added" or "v1.0".
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

undo ~178

Rewind the workspace cursor by one, re-materializing the state as it was before the last mutation. Does NOT delete any ops — redo will fast-forward. Calling undo at the workspace genesis (cursor === 0, only the CreateWorkspace op is in scope) is a no-op that surfaces an error rather than silently doing nothing. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

NameTypeReqDescription
confirmedboolean–Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Undo rewinds the most recent change; redo restores it.
map_idstringyes–
rationalestring–Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

No output schema declared.

No examples provided.

Install

How do I install the ShowMeOnMap MCP server?

ShowMeOnMap is a hosted endpoint at https://showmeonmap.com/api/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 · showmeonmap.com

# add to Claude Code
claude mcp add --transport http com-showmeonmap-maps 'https://showmeonmap.com/api/mcp'
Common questions

What is the ShowMeOnMap MCP server?

ShowMeOnMap is an MCP server listed in the public MCP registry as com.showmeonmap/maps. Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools. This page covers its hosted endpoint (https://showmeonmap.com/api/mcp).

Is the ShowMeOnMap MCP server safe to use?

ShowMeOnMap scores 93 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 ShowMeOnMap MCP server expose?

ShowMeOnMap exposes 32 tools: get_map_view, build_map, osm_features, analyze, mutate_map, and 27 more. Their descriptions and schemas cost roughly 7,424 tokens of context every time the server is loaded.

Does the ShowMeOnMap MCP server require authentication?

Yes. ShowMeOnMap 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 ShowMeOnMap MCP server still maintained?

ShowMeOnMap is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.