Wherebox
NPM · @WHEREBOX/MCP · 2 COMPONENTS
Render static locator maps (area highlight, places, routes) and search places from AI assistants.
Available components
Last scanned (18 hours ago)
Scores higher than 44% of npm servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- 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 3779 tokens (~130/item across 29 items; 4 tools + 25 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 9 Nov 26 66
First indexed and scored.
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 21 Nov 2026 · Analysed npm/@wherebox/mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_map_url Get a map image URL ~971
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
render_map Render a map ~958
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
search_areas Search areas ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most results to return. |
| q | string | yes | Name to look up, in any language or spelling (accents optional), e.g. "Zlínský kraj", "Chriby". |
No output schema declared.
No examples provided.
search_places Search places ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most results to return. |
| q | string | yes | Name to look up, in any language or spelling (accents optional), e.g. "Zlínský kraj", "Chriby". |
No output schema declared.
No examples provided.
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.
npm · @wherebox/mcp
claude mcp add wherebox-wherebox -- npx -y @wherebox/mcp
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.