# dev.overspan/mcp (npm · overspan-mcp)

OpenStreetMap queries as MCP tools, served by the Overspan hosted Overpass API.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `overspan-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/dev-overspan-mcp/overspan-mcp.md), [page](https://verifymcp.io/servers/dev-overspan-mcp/overspan-mcp)

## Channel facts

- Registry: `npm`
- Package: `overspan-mcp`
- Version: `0.1.2`
- 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-09-20.

- **Supply Chain Security**: 98/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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 759 tokens (~108/item across 7 items; 5 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add dev-overspan-mcp -- npx -y overspan-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-overspan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "overspan-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-overspan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "overspan-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-overspan-mcp -- npx -y overspan-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-overspan-mcp --command npx --arg -y --arg overspan-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-overspan-mcp:
    command: "npx"
    args: ["-y", "overspan-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-overspan-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "overspan-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-overspan-mcp -t stdio -c npx -a -y overspan-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-overspan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "overspan-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-09-20 (score 82, +1)

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

### 2026-09-18 (score 81, +1)

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

### 2026-09-16 (score 80, +1)

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

### 2026-09-14 (score 79, +1)

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

### 2026-09-11 (score 78, +1)

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

### 2026-09-09 (score 77, +1)

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

### 2026-09-07 (score 76, +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-09-05 (score 75, +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.

## MCP tools (5)

### `overpass_query` (~167 tokens)

Run raw Overpass QL

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.

Input parameters:

- `query` (string, required): A complete Overpass QL query, e.g. [out:json][timeout:25];nwr[amenity=cafe](around:500,-36.85,174.76);out center 25;

### `find_nearby` (~165 tokens)

Find features near a point

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.

Input parameters:

- `lat` (number, required): Latitude of the centre point
- `limit` (integer): Maximum elements to return (default 25)
- `lon` (number, required): Longitude of the centre point
- `radius_m` (number): Search radius in metres (default 500)
- `tags` (object, required): OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}.

### `features_in_bbox` (~149 tokens)

Find features in a bounding box

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.

Input parameters:

- `east` (number, required)
- `limit` (integer): Maximum elements to return (default 25)
- `north` (number, required)
- `south` (number, required)
- `tags` (object, required): OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}.
- `west` (number, required)

### `count_features` (~170 tokens)

Count matching features

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

Input parameters:

- `east` (number)
- `lat` (number)
- `lon` (number)
- `north` (number)
- `radius_m` (number): Radius in metres, used with lat/lon (default 500)
- `south` (number)
- `tags` (object, required): OpenStreetMap tag filters, all must match. Use "*" as the value to match any value, e.g. {"amenity": "cafe"} or {"opening_hours": "*"}.
- `west` (number)

### `get_usage` (~44 tokens)

Check Overspan usage and limits

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.

## Diagnostics

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

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 56
- 2026-08-26: 38

## Common questions

### 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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/overspan-mcp
- Socket report: https://socket.dev/npm/package/overspan-mcp
- Repository: https://github.com/julesmaxxx/overspan-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-overspan-mcp/overspan-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-overspan-mcp/overspan-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-overspan-mcp/overspan-mcp