# ShowMeOnMap (remote · showmeonmap.com)

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

- Trust score: 74/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `showmeonmap.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp.md), [page](https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp)
- npm · `@showmeonmap/mcp`: 63/100, [markdown](https://verifymcp.io/servers/com-showmeonmap-maps/showmeonmap-mcp.md), [page](https://verifymcp.io/servers/com-showmeonmap-maps/showmeonmap-mcp)

## Channel facts

- Endpoint: `https://showmeonmap.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4719 tokens (~188/item across 25 items; 24 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-showmeonmap-maps https://showmeonmap.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-showmeonmap-maps]
url = "https://showmeonmap.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-showmeonmap-maps": {
      "type": "remote",
      "url": "https://showmeonmap.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-showmeonmap-maps --url https://showmeonmap.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-showmeonmap-maps:
    url: "https://showmeonmap.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-showmeonmap-maps": {
      "type": "http",
      "url": "https://showmeonmap.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 72, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

- [security] Tool “export_layer_data” rewrote its description, which is the text the model reads

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (24)

### `build_map` (~172 tokens)

Build a map

Create a new workspace from a natural-language query. Returns a map_id you can pass to mutate_map or get_state for follow-up actions. For the full Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept, fetch the MCP resource at showmeonmap://docs/workspace-ops-spec — do NOT guess the shapes.

Input parameters:

- `query` (string, required): Natural language: "coffee shops in Tokyo", "GDP by country", "volcanoes in Indonesia", etc.
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `mutate_map` (~192 tokens)

Mutate a map

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. For the full Op catalog and predicate grammar, fetch the MCP resource showmeonmap://docs/workspace-ops-spec.

Input parameters:

- `instruction` (string, required): e.g., "filter to where magnitude is greater than 5", "change basemap to dark"
- `map_id` (string, required): map_id from a prior build_map call
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `get_state` (~94 tokens)

Read map state

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

Input parameters:

- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `add_layer` (~282 tokens)

Add a layer (direct)

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, ... }. Prefer this when you already have a structured plan; otherwise use mutate_map. For the full LayerPlan and Op spec, fetch the MCP resource showmeonmap://docs/workspace-ops-spec.

Input parameters:

- `intent` (string): 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-…
- `layerPlan` (object, required): Full LayerPlan object. Must include id, title, source, viz, geometry.
- `map_id` (string, required): map_id from a prior build_map call
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `add_fusion_layer` (~233 tokens)

Add bivariate fusion layer

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 (call build_map or add_layer first). 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, rationale.

Input parameters:

- `layer_a_id` (string, required)
- `layer_b_id` (string, required)
- `map_id` (string, required)
- `mode` (string)
- `new_layer_id` (string)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…
- `value_field_a` (string)
- `value_field_b` (string)

### `correlate_layers` (~201 tokens)

Compute correlation between two layers

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. Use this when you want a numeric answer without rendering; use add_fusion_layer when the user wants the visualization. Required: map_id, layer_a_id, layer_b_id, rationale.

Input parameters:

- `layer_a_id` (string, required)
- `layer_b_id` (string, required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…
- `value_field_a` (string)
- `value_field_b` (string)

### `filter_layer` (~306 tokens)

Filter a layer (direct)

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

Input parameters:

- `append` (boolean): Default true. false replaces the layer's existing filter chain.
- `intent` (string): 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…
- `layerId` (string, required): id of the layer to filter
- `map_id` (string, required)
- `predicate` (object, required): Predicate 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…
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `select_within` (~194 tokens)

Subset a layer to a polygon selection

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."

Input parameters:

- `inheritStyle` (boolean): Default true. false emits a new layer with minimal default styling.
- `map_id` (string, required)
- `newLayerId` (string, required): Id for the new layer. Must not already be in use in this workspace.
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…
- `selection` (object, required): GeoJSON Polygon or MultiPolygon in [lng,lat] coordinate order.
- `sourceLayerId` (string, required)

### `query_features` (~255 tokens)

Query features from a layer (read-only)

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.

Input parameters:

- `layerId` (string, required)
- `limit` (integer): Default 100, max 1000. Response sets `truncated:true` when clipped.
- `map_id` (string, required)
- `predicate` (object, required): Predicate 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…
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `remove_layer` (~198 tokens)

Remove a layer (direct, destructive)

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.

Input parameters:

- `confirmed` (boolean): 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…
- `layerId` (string, required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `clear_filters` (~188 tokens)

Clear all filters on a layer (direct, gated)

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.

Input parameters:

- `confirmed` (boolean): Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Wiping a filter chain is recoverable via undo, but autonomous agents lack a UI surfa…
- `layerId` (string, required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `rename_layer` (~167 tokens)

Rename a layer (direct)

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.

Input parameters:

- `map_id` (string, required)
- `newLayerId` (string, required): New id. Must be unique within the workspace.
- `oldLayerId` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `restyle_layer` (~172 tokens)

Restyle a layer (direct)

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.

Input parameters:

- `color` (string): CSS color string: hex (#RRGGBB), rgb/rgba, or named color.
- `layerId` (string, required)
- `map_id` (string, required)
- `opacity` (number): 0 (transparent) to 1 (opaque).
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `set_camera` (~185 tokens)

Set the map camera (direct)

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). Use for "zoom to Japan", "center on Paris at z=10", or finishing a drill-down after filter_layer. Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip.

Input parameters:

- `camera` (required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `set_time` (~224 tokens)

Set the time window (direct)

Override the current time-range filter. Latest set_time op wins during replay. Use for "filter to 2020-2024" or "show only the last 7 days" intents. 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.

Input parameters:

- `field` (string, required): Feature property carrying the time value (e.g. "date", "year", "timestamp").
- `format` (string): How rangeStart/rangeEnd encode time. Default: unix_ms at render time.
- `map_id` (string, required)
- `rangeEnd` (number, required): Inclusive upper bound of the visible window.
- `rangeStart` (number, required): Inclusive lower bound of the visible window.
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `tag` (~152 tokens)

Save a named checkpoint (direct)

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.

Input parameters:

- `map_id` (string, required)
- `name` (string, required): Checkpoint label, e.g. "before EV layer added" or "v1.0".
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `add_annotation` (~187 tokens)

Place an annotation on the map (direct)

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).

Input parameters:

- `color` (string): Optional CSS color for the marker + label.
- `coords` (array, required): [lng, lat] in WGS84.
- `id` (string, required): Stable id for this annotation — caller-supplied.
- `label` (string): Optional text rendered at the point.
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `remove_annotation` (~137 tokens)

Remove an annotation (direct)

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).

Input parameters:

- `annotationId` (string, required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `export_workspace` (~150 tokens)

Export the workspace JSON

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. Use this when you want the full raw state for serialization; use get_state when you want the compact envelope for display.

Input parameters:

- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `export_layer_data` (~183 tokens)

Export layer data

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 — treat it as shareable-forever, not temporary. Required: map_id, layer_id, format, rationale.

Input parameters:

- `format` (string, required)
- `layer_id` (string, required)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `export_image` (~174 tokens)

Export map as image

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, rationale. Optional: format (png default), legend (true default).

Input parameters:

- `format` (string)
- `legend` (boolean)
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `undo` (~212 tokens)

Undo the most recent op (gated)

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.

Input parameters:

- `confirmed` (boolean): Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Autonomous undo without user intent is a footgun — an agent that decides to "fix" so…
- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `redo` (~151 tokens)

Redo a previously-undone op

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).

Input parameters:

- `map_id` (string, required)
- `rationale` (string, required): Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. "add wildfire layer for the user's California query". Required on every call. Stored in the operations log so ma…

### `report_blocker` (~258 tokens)

Report a blocker (agent feedback)

Tell the ShowMeOnMap team your agent hit something it could not accomplish — an unsupported intent, a missing tool, an unclear schema, an op that failed in a confusing way. Use this when build_map / mutate_map / a direct-op tool returns something you cannot recover from, OR when you would have wanted a different tool to exist. Records the report to a server-side log; does not unblock the current session, but feeds future capability work. No map_id required — file the report even if no map was built.

Input parameters:

- `map_id` (string): Optional. The map_id you were working on, if any.
- `suggested_capability` (string): Optional. A new tool, op, or schema field that would have unblocked you.
- `what_i_tried` (string, required): Which tools / inputs you attempted, in order. Be specific — tool name + key arg shape is ideal.
- `what_i_was_trying` (string, required): High-level intent in one or two sentences. e.g. "merge two filtered choropleths into a fused bivariate map".
- `where_i_got_stuck` (string, required): The specific failure: what came back, what was missing, why you could not proceed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 73
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://showmeonmap.com/api/mcp
- Authorisation metadata: https://showmeonmap.com/.well-known/oauth-protected-resource/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-showmeonmap-maps/api-mcp