# NAPSPAN (remote · api.napspan.com)

European NAP road data (DATEX II): incidents, roadworks, cameras, truck parking. Paid API key.

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

## Components

- remote · `api.napspan.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp.md), [page](https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp)

## Channel facts

- Endpoint: `https://api.napspan.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

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

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1329 tokens (~94/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 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 NAPSPAN MCP server?

NAPSPAN is a hosted endpoint at https://api.napspan.com/api/v1/mcp, so there is nothing to install locally. 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 --transport http com-napspan-traffic 'https://api.napspan.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-napspan-traffic": {
      "url": "https://api.napspan.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-napspan-traffic": {
      "type": "http",
      "url": "https://api.napspan.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-napspan-traffic]
url = "https://api.napspan.com/api/v1/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-napspan-traffic --url 'https://api.napspan.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-napspan-traffic:
    url: "https://api.napspan.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-napspan-traffic": {
      "Transport": "http",
      "Url": "https://api.napspan.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-napspan-traffic -t streamable-http -u 'https://api.napspan.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-napspan-traffic": {
      "type": "http",
      "url": "https://api.napspan.com/api/v1/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-11-21 (score 82, +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-11-19 (score 81, +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-17 (score 80, +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-15 (score 79, +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-13 (score 78, +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-10 (score 77, +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-11-09 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 76)

First indexed and scored.

## MCP tools (14)

### `get_coverage` (~36 tokens)

Per-jurisdiction counts of what data is available, by type.

Input parameters:

- `jurisdiction` (string): jurisdiction code; omit for all

### `get_event` (~45 tokens)

Full detail of one traffic event by id.

Input parameters:

- `id` (string, required): the id from a search result
- `include_geometry` (boolean): keep geometry in the output (large)

### `get_event_hotspots` (~66 tokens)

Geographic clusters of traffic events. Needs a plan with analytics.

Input parameters:

- `from` (string): ISO 8601 lower bound
- `jurisdiction` (string): jurisdiction code
- `to` (string): ISO 8601 upper bound
- `type` (string): event type

### `get_event_trends` (~100 tokens)

Event counts over time. Needs a plan with analytics.

Input parameters:

- `bucket` (string): time bucket, e.g. day or week
- `from` (string): ISO 8601 lower bound
- `group_by` (string): grouping dimension
- `jurisdiction` (string): jurisdiction code
- `severity` (string): severity filter
- `to` (string): ISO 8601 upper bound
- `type` (string): event type

### `get_feature_details` (~55 tokens)

Full detail of one feature by id (for cameras, the current image/stream URLs).

Input parameters:

- `id` (string, required): the id from a search result
- `include_geometry` (boolean): keep geometry in the output (large)

### `get_fuel_prices` (~117 tokens)

Fuel price series by jurisdiction, country and fuel type.

Input parameters:

- `country` (string): country code
- `from` (string): ISO 8601 date lower bound
- `fuel_type` (string): fuel type, e.g. diesel
- `jurisdiction` (string): jurisdiction or region code
- `latest` (null|boolean): only the latest price per series
- `limit` (integer): results to return, default 25, max 100
- `to` (string): ISO 8601 date upper bound

### `get_status` (~16 tokens)

Service status: tracked resources and availability.

### `get_truck_corridor` (~122 tokens)

Truck-relevant restrictions, clearances and events along a straight corridor between two points. Needs a plan with truck data.

Input parameters:

- `buffer_km` (null|number): corridor half-width in km
- `from_lat` (number, required): origin latitude
- `from_lng` (number, required): origin longitude
- `jurisdiction` (string): restrict to one jurisdiction
- `limit` (integer): results to return, default 25, max 100
- `to_lat` (number, required): destination latitude
- `to_lng` (number, required): destination longitude

### `list_feature_groups` (~20 tokens)

List feature groups, for search_features' group filter.

### `list_feature_types` (~27 tokens)

List feature types (cameras, weather stations, truck parking, restrictions...) with counts.

### `list_jurisdictions` (~45 tokens)

List the jurisdictions (states, provinces, countries, regions) with their codes.

Input parameters:

- `scope` (string): optional scope filter as accepted by GET /jurisdictions

### `plan_truck_route` (~143 tokens)

Compute a truck route with hazard warnings along it. Each call counts against the plan's monthly routing quota.

Input parameters:

- `departure_time` (string): ISO 8601 or now
- `destination` (object, required): end point
- `include_geometry` (boolean): keep the route polyline in the output (large)
- `origin` (object, required): start point
- `truck` (object, required): truck profile as in POST /routing/route, e.g. {"weight_t":36,"height_m":4.1,"length_m":21}; may be {}
- `units` (string): metric or imperial
- `waypoints` (null|array): intermediate stops

### `search_events` (~249 tokens)

Search traffic events (incidents, construction, closures) by jurisdiction, area, type and time.

Input parameters:

- `bbox` (string): bounding box min_lng,min_lat,max_lng,max_lat
- `include_geometry` (boolean): keep geometry in the output (large)
- `jurisdiction` (string): jurisdiction code, comma-separated for several
- `lat` (null|number): centre latitude for a radius search (with lng and radius_km)
- `limit` (integer): results to return, default 25, max 100
- `lng` (null|number): centre longitude for a radius search
- `offset` (integer): results to skip for the next page
- `radius_km` (null|number): search radius in km
- `road` (string): road name or number filter
- `severity` (string): severity filter
- `start_time_from` (string): ISO 8601 lower bound on start time
- `start_time_to` (string): ISO 8601 upper bound on start time
- `status` (string): status filter, e.g. active
- `type` (string): event type, e.g. incident, construction, closure

### `search_features` (~220 tokens)

Search road features (cameras, weather stations, signs, truck parking, bridge clearances, restrictions...). Page with cursor.

Input parameters:

- `active` (null|boolean): only active features (default true upstream)
- `bbox` (string): bounding box min_lng,min_lat,max_lng,max_lat
- `cursor` (string): next_cursor from the previous page
- `group` (string): feature group id from list_feature_groups
- `include_geometry` (boolean): keep geometry in the output (large)
- `jurisdiction` (string): jurisdiction code, comma-separated for several
- `lat` (null|number): centre latitude for a radius search (with lng and radius_km)
- `limit` (integer): results to return, default 25, max 100
- `lng` (null|number): centre longitude for a radius search
- `radius_km` (null|number): search radius in km
- `type` (string): feature type from list_feature_types, e.g. cameras, truck_parking, bridge_clearances

## Diagnostics

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

## Score history

- 2026-11-22: 82
- 2026-11-21: 82
- 2026-11-20: 81
- 2026-11-19: 81
- 2026-11-18: 80
- 2026-11-17: 80
- 2026-11-16: 79
- 2026-11-15: 79
- 2026-11-14: 78
- 2026-11-13: 78
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 77
- 2026-11-09: 76
- 2026-11-08: 76

## Common questions

### What is the NAPSPAN MCP server?

NAPSPAN is an MCP server listed in the public MCP registry as com.napspan/traffic. European NAP road data (DATEX II): incidents, roadworks, cameras, truck parking. Paid API key. This page covers its hosted endpoint (https://api.napspan.com/api/v1/mcp).

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

NAPSPAN scores 82 out of 100 on VerifyMCP. 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 NAPSPAN MCP server expose?

NAPSPAN exposes 14 tools: get_coverage, get_event, get_event_hotspots, get_event_trends, get_feature_details, and 9 more. Their descriptions and schemas cost roughly 1,261 tokens of context every time the server is loaded.

### Does the NAPSPAN MCP server require authentication?

Yes. NAPSPAN asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the NAPSPAN MCP server still maintained?

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

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

VerifyMCP ran 13 checks on NAPSPAN, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.napspan.com/api/v1/mcp
- Authorisation metadata: https://api.napspan.com/.well-known/oauth-protected-resource/api/v1/mcp
- Website: https://napspan.com/docs.html#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-napspan-traffic/api-v1-mcp
