dev.overspan/mcp
NPM · OVERSPAN-MCP
OpenStreetMap queries as MCP tools, served by the Overspan hosted Overpass API.
Available components
Last scanned (17 minutes ago)
Scores higher than 61% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 70 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 759 tokens (~108/item across 7 items; 5 tools + 2 resources), lean.Pass
- 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 Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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
- We read all 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 · Analysed npm/overspan-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
count_features Count matching features ~170
Count OpenStreetMap features matching tag filters in an area without returning them. Cheap. Use this before pulling data when the result size is unknown. Give either a point (lat, lon, radius_m) or a bounding box (south, west, north, east).
| Name | Type | Req | Description |
|---|---|---|---|
| east | number | – | – |
| lat | number | – | – |
| lon | number | – | – |
| north | number | – | – |
| radius_m | number | – | Radius in metres, used with lat/lon (default 500) |
| south | number | – | – |
| tags | object | yes | OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}. |
| west | number | – | – |
No output schema declared.
No examples provided.
features_in_bbox Find features in a bounding box ~149
Find OpenStreetMap features matching tag filters inside a bounding box (south, west, north, east in decimal degrees). Returns up to 'limit' elements with their tags and a centre coordinate. Keep boxes small; for city-sized areas call count_features first.
| Name | Type | Req | Description |
|---|---|---|---|
| east | number | yes | – |
| limit | integer | – | Maximum elements to return (default 25) |
| north | number | yes | – |
| south | number | yes | – |
| tags | object | yes | OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}. |
| west | number | yes | – |
No output schema declared.
No examples provided.
find_nearby Find features near a point ~165
Find OpenStreetMap features matching tag filters within a radius of a point. Returns up to 'limit' elements with their tags and a centre coordinate. Good first tool for questions like 'what cafes are near X'. For larger or unknown result sets, call count_features first.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude of the centre point |
| limit | integer | – | Maximum elements to return (default 25) |
| lon | number | yes | Longitude of the centre point |
| radius_m | number | – | Search radius in metres (default 500) |
| tags | object | yes | OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}. |
No output schema declared.
No examples provided.
get_usage Check Overspan usage and limits ~44
Check this API key's tier, its limits, month-to-date quota, and recent request history. Does not consume query quota. Use it to pace yourself when running many queries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
overpass_query Run raw Overpass QL ~167
Run a raw Overpass QL query against the Overspan hosted Overpass API (full-planet OpenStreetMap data, minutes behind live). Use this when the helper tools are too narrow. Always bound the query to an area and cap the output (for example: out center 25;). Start with [out:json]. Queries without [timeout:] get 25 seconds. Read the overspan://overpass-ql resource for syntax and the overspan://differences resource for how this server differs from the public ones.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A complete Overpass QL query, e.g. [out:json][timeout:25];nwr[amenity=cafe](around:500,-36.85,174.76);out center 25; |
No output schema declared.
No examples provided.
How do I install the dev.overspan/mcp server?
dev.overspan/mcp runs locally as an npm package, launched with npx -y overspan-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 · overspan-mcp
claude mcp add dev-overspan-mcp -- npx -y overspan-mcp
What is the dev.overspan/mcp server?
dev.overspan/mcp is listed in the public MCP registry as dev.overspan/mcp. OpenStreetMap queries as MCP tools, served by the Overspan hosted Overpass API. This page covers its npm package (overspan-mcp).
Is the dev.overspan/mcp server safe to use?
dev.overspan/mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 dev.overspan/mcp server expose?
dev.overspan/mcp exposes 5 tools: overpass_query, find_nearby, features_in_bbox, count_features, get_usage. Their descriptions and schemas cost roughly 695 tokens of context every time the server is loaded.
Is the dev.overspan/mcp server still maintained?
dev.overspan/mcp 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.
What licence is the dev.overspan/mcp server under?
dev.overspan/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.