# Wherebox (npm · @wherebox/mcp)

Render static locator maps (area highlight, places, routes) and search places from AI assistants.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.wherebox.dev`: 37/100, [markdown](https://verifymcp.io/servers/wherebox-wherebox/api.md), [page](https://verifymcp.io/servers/wherebox-wherebox/api)
- npm · `@wherebox/mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp.md), [page](https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp)

## Channel facts

- Registry: `npm`
- Package: `@wherebox/mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 81/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 3779 tokens (~130/item across 29 items; 4 tools + 25 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Wherebox MCP server?

Wherebox runs locally as an npm package, launched with npx -y @wherebox/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wherebox-wherebox -- npx -y @wherebox/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "wherebox-wherebox": {
      "command": "npx",
      "args": [
        "-y",
        "@wherebox/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wherebox-wherebox": {
      "command": "npx",
      "args": [
        "-y",
        "@wherebox/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wherebox-wherebox -- npx -y @wherebox/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wherebox-wherebox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@wherebox/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wherebox-wherebox --command npx --arg -y --arg @wherebox/mcp
```

### Hermes

```yaml
mcp_servers:
  wherebox-wherebox:
    command: "npx"
    args: ["-y", "@wherebox/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "wherebox-wherebox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@wherebox/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add wherebox-wherebox -t stdio -c npx -a -y @wherebox/mcp
```

### Other

```json
{
  "mcpServers": {
    "wherebox-wherebox": {
      "command": "npx",
      "args": [
        "-y",
        "@wherebox/mcp"
      ]
    }
  }
}
```

## 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-11-20 (score 72, +1)

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

### 2026-11-18 (score 71, +1)

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

### 2026-11-16 (score 70, +1)

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

### 2026-11-14 (score 69, +1)

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

### 2026-11-12 (score 68, +1)

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

### 2026-11-10 (score 67, +1)

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

### 2026-11-09 (score 66)

First indexed and scored.

## MCP tools (4)

### `render_map` (~958 tokens)

Render a map

Render a static map image and return it, so you can see it, together with its permanent public URL. Use this to design a map: look at the image and call again with a refined spec until it is right. Arguments are a Wherebox MapSpec: give at least one of `area` (a name or an id such as `iso:CZ-72`, `osm:r51684`), `pois`, `routes` or `bounds`. Defaults: 600×400 CSS px, PNG, the shaded-relief basemap, labels in local language (`lang` for others). Points take `lat`+`lon` or a `place` name; routes take `from`/`to` and default to a geodesic line (routed `car`/`bike`/`foot` profiles need a routing engine and plan). Each new map counts as one render toward the monthly quota; repeating an identical spec is served from cache for free. Ambiguous or unknown names come back as an error listing candidates or close matches.

Input parameters:

- `area`: The area to frame and highlight. Ambiguous names return 409 with candidates.
- `basemap` (object): The map underneath: a built-in preset or your own style.
- `bounds` (array): Explicit frame `[west, south, east, north]`; overrides automatic framing. Cannot be combined with `center`/`zoom`.
- `center` (object): Center of the map. With `zoom`, this is an exact camera (as in other static map APIs) and nothing else affects the frame. Without `zoom`, the zoom is chosen so the area, routes, shapes and points fit…
- `format` (string): Image format (GET can also use the path extension: /v1/map.png, .jpg, .webp).
- `height` (integer): Image height in CSS px, including the title band if any.
- `highlight` (object): How the area stands out. Unset fields use the basemap preset's defaults (see the presets reference).
- `lang` (string): Label language (ISO 639-1). Default: local names (Deutschland, Polska), as on Wikipedia locator maps.
- `legend` (object): A classic map legend. With it, every labeled point (and labeled route end) is drawn as a numbered circle instead of its label, and the panel lists "number – label" pairs on the chosen side. The panel…
- `neighbors` (object): Label the countries around the area (needs an `area`).
- `padding` (number): Space around the framed content as a fraction of the image size.
- `pois` (array): Points with markers and labels (up to 50).
- `projection` (string): Map projection. `mercator` is the usual flat web map. `globe` draws an orthographic globe, which keeps continent-spanning routes and high latitudes true to shape; the content must fit on one hemisphe…
- `routes` (array): Routes to draw (GET supports one; POST up to 10).
- `scale` (integer): Pixel ratio for high-DPI output (2 = retina).
- `title` (object): A title band, drawn inside the requested width×height (the map gets the rest).
- `width` (integer): Image width in CSS px (the output is width × `scale` pixels).
- `worldview` (string): Draw country borders as this country sees them (ISO 3166-1 alpha-2, e.g. `in`, `cn`, `us`, `ma`). Replaces the basemap's country and disputed borders with Natural Earth's borders for that worldview,…
- `zoom` (number): Zoom level, 0 (whole world) to 22, in the usual web-map zoom units (512 px tiles, as MapLibre and Mapbox GL: at zoom z the world is 512·2^z CSS px wide). With `center`, an exact camera; without `cent…

### `get_map_url` (~971 tokens)

Get a map image URL

Render a map (or reuse the cached one) and return only its permanent, public image URL (`/v1/images/<hash>.<ext>`) for embedding in Markdown, HTML or documents, without the image bytes. The URL is content-addressed: it never changes for the same spec, needs no key, and anyone with it can view the image. Arguments are a Wherebox MapSpec: give at least one of `area` (a name or an id such as `iso:CZ-72`, `osm:r51684`), `pois`, `routes` or `bounds`. Defaults: 600×400 CSS px, PNG, the shaded-relief basemap, labels in local language (`lang` for others). Points take `lat`+`lon` or a `place` name; routes take `from`/`to` and default to a geodesic line (routed `car`/`bike`/`foot` profiles need a routing engine and plan). Each new map counts as one render toward the monthly quota; repeating an identical spec is served from cache for free.

Input parameters:

- `area`: The area to frame and highlight. Ambiguous names return 409 with candidates.
- `basemap` (object): The map underneath: a built-in preset or your own style.
- `bounds` (array): Explicit frame `[west, south, east, north]`; overrides automatic framing. Cannot be combined with `center`/`zoom`.
- `center` (object): Center of the map. With `zoom`, this is an exact camera (as in other static map APIs) and nothing else affects the frame. Without `zoom`, the zoom is chosen so the area, routes, shapes and points fit…
- `format` (string): Image format (GET can also use the path extension: /v1/map.png, .jpg, .webp).
- `height` (integer): Image height in CSS px, including the title band if any.
- `highlight` (object): How the area stands out. Unset fields use the basemap preset's defaults (see the presets reference).
- `lang` (string): Label language (ISO 639-1). Default: local names (Deutschland, Polska), as on Wikipedia locator maps.
- `legend` (object): A classic map legend. With it, every labeled point (and labeled route end) is drawn as a numbered circle instead of its label, and the panel lists "number – label" pairs on the chosen side. The panel…
- `neighbors` (object): Label the countries around the area (needs an `area`).
- `padding` (number): Space around the framed content as a fraction of the image size.
- `pois` (array): Points with markers and labels (up to 50).
- `projection` (string): Map projection. `mercator` is the usual flat web map. `globe` draws an orthographic globe, which keeps continent-spanning routes and high latitudes true to shape; the content must fit on one hemisphe…
- `routes` (array): Routes to draw (GET supports one; POST up to 10).
- `scale` (integer): Pixel ratio for high-DPI output (2 = retina).
- `title` (object): A title band, drawn inside the requested width×height (the map gets the rest).
- `width` (integer): Image width in CSS px (the output is width × `scale` pixels).
- `worldview` (string): Draw country borders as this country sees them (ISO 3166-1 alpha-2, e.g. `in`, `cn`, `us`, `ma`). Replaces the basemap's country and disputed borders with Natural Earth's borders for that worldview,…
- `zoom` (number): Zoom level, 0 (whole world) to 22, in the usual web-map zoom units (512 px tiles, as MapLibre and Mapbox GL: at zoom z the world is 512·2^z CSS px wide). With `center`, an exact camera; without `cent…

### `search_areas` (~143 tokens)

Search areas

Find admin areas (countries, regions, districts, municipalities) by name. Each result has a `ref` (e.g. "osm:r439539") to pass as `area` or `highlight.subArea`, its admin level, and `context`: its parent areas ("Česko › Liberecký kraj › …"), which tells same-named areas apart. Use it before rendering when a name may be ambiguous.

Input parameters:

- `limit` (integer): Most results to return.
- `q` (string, required): Name to look up, in any language or spelling (accents optional), e.g. "Zlínský kraj", "Chriby".

### `search_places` (~136 tokens)

Search places

Find named places (cities, villages, peaks, mountain ranges…) by name. Each result has coordinates and `context`: the areas containing it, which tells same-named places apart. Pass the chosen place as `{"lat": …, "lon": …}` in `pois` or route `from`/`to` (exact), or by `place` name when the name is unique.

Input parameters:

- `limit` (integer): Most results to return.
- `q` (string, required): Name to look up, in any language or spelling (accents optional), e.g. "Zlínský kraj", "Chriby".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 69
- 2026-11-14: 69
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 66

## Common questions

### What is the Wherebox MCP server?

Wherebox is an MCP server listed in the public MCP registry as io.github.wherebox/wherebox. Render static locator maps (area highlight, places, routes) and search places from AI assistants. This page covers its npm package (@wherebox/mcp).

### Is the Wherebox MCP server safe to use?

Wherebox scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Wherebox MCP server expose?

Wherebox exposes 4 tools: render_map, get_map_url, search_areas, search_places. Their descriptions and schemas cost roughly 2,208 tokens of context every time the server is loaded.

### Is the Wherebox MCP server still maintained?

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

### What licence is the Wherebox MCP server under?

Wherebox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Wherebox MCP server?

VerifyMCP ran 15 checks on Wherebox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Wherebox: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@wherebox/mcp
- Socket report: https://socket.dev/npm/package/@wherebox/mcp
- Website: https://wherebox.dev/
- Changelog RSS feed: https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wherebox-wherebox/wherebox-mcp
