NAPSPAN
Server Details
European NAP road data (DATEX II): incidents, roadworks, cameras, truck parking. Paid API key.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Score is being calculated.
Available Tools
14 toolsget_coverageInspect
Per-jurisdiction counts of what data is available, by type.
| Name | Required | Description | Default |
|---|---|---|---|
| jurisdiction | No | jurisdiction code; omit for all |
get_eventInspect
Full detail of one traffic event by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the id from a search result | |
| include_geometry | No | keep geometry in the output (large) |
get_event_hotspotsInspect
Geographic clusters of traffic events. Needs a plan with analytics.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ISO 8601 upper bound | |
| from | No | ISO 8601 lower bound | |
| type | No | event type | |
| jurisdiction | No | jurisdiction code |
get_event_trendsInspect
Event counts over time. Needs a plan with analytics.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ISO 8601 upper bound | |
| from | No | ISO 8601 lower bound | |
| type | No | event type | |
| bucket | No | time bucket, e.g. day or week | |
| group_by | No | grouping dimension | |
| severity | No | severity filter | |
| jurisdiction | No | jurisdiction code |
get_feature_detailsInspect
Full detail of one feature by id (for cameras, the current image/stream URLs).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the id from a search result | |
| include_geometry | No | keep geometry in the output (large) |
get_fuel_pricesInspect
Fuel price series by jurisdiction, country and fuel type.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ISO 8601 date upper bound | |
| from | No | ISO 8601 date lower bound | |
| limit | No | results to return, default 25, max 100 | |
| latest | No | only the latest price per series | |
| country | No | country code | |
| fuel_type | No | fuel type, e.g. diesel | |
| jurisdiction | No | jurisdiction or region code |
get_statusInspect
Service status: tracked resources and availability.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_truck_corridorInspect
Truck-relevant restrictions, clearances and events along a straight corridor between two points. Needs a plan with truck data.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | results to return, default 25, max 100 | |
| to_lat | Yes | destination latitude | |
| to_lng | Yes | destination longitude | |
| from_lat | Yes | origin latitude | |
| from_lng | Yes | origin longitude | |
| buffer_km | No | corridor half-width in km | |
| jurisdiction | No | restrict to one jurisdiction |
list_feature_groupsInspect
List feature groups, for search_features' group filter.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_feature_typesInspect
List feature types (cameras, weather stations, truck parking, restrictions...) with counts.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_jurisdictionsInspect
List the jurisdictions (states, provinces, countries, regions) with their codes.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | optional scope filter as accepted by GET /jurisdictions |
plan_truck_routeInspect
Compute a truck route with hazard warnings along it. Each call counts against the plan's monthly routing quota.
| Name | Required | Description | Default |
|---|---|---|---|
| truck | Yes | truck profile as in POST /routing/route, e.g. {"weight_t":36,"height_m":4.1,"length_m":21}; may be {} | |
| units | No | metric or imperial | |
| origin | Yes | start point | |
| waypoints | No | intermediate stops | |
| destination | Yes | end point | |
| departure_time | No | ISO 8601 or now | |
| include_geometry | No | keep the route polyline in the output (large) |
search_eventsInspect
Search traffic events (incidents, construction, closures) by jurisdiction, area, type and time.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | centre latitude for a radius search (with lng and radius_km) | |
| lng | No | centre longitude for a radius search | |
| bbox | No | bounding box min_lng,min_lat,max_lng,max_lat | |
| road | No | road name or number filter | |
| type | No | event type, e.g. incident, construction, closure | |
| limit | No | results to return, default 25, max 100 | |
| offset | No | results to skip for the next page | |
| status | No | status filter, e.g. active | |
| severity | No | severity filter | |
| radius_km | No | search radius in km | |
| jurisdiction | No | jurisdiction code, comma-separated for several | |
| start_time_to | No | ISO 8601 upper bound on start time | |
| start_time_from | No | ISO 8601 lower bound on start time | |
| include_geometry | No | keep geometry in the output (large) |
search_featuresInspect
Search road features (cameras, weather stations, signs, truck parking, bridge clearances, restrictions...). Page with cursor.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | centre latitude for a radius search (with lng and radius_km) | |
| lng | No | centre longitude for a radius search | |
| bbox | No | bounding box min_lng,min_lat,max_lng,max_lat | |
| type | No | feature type from list_feature_types, e.g. cameras, truck_parking, bridge_clearances | |
| group | No | feature group id from list_feature_groups | |
| limit | No | results to return, default 25, max 100 | |
| active | No | only active features (default true upstream) | |
| cursor | No | next_cursor from the previous page | |
| radius_km | No | search radius in km | |
| jurisdiction | No | jurisdiction code, comma-separated for several | |
| include_geometry | No | keep geometry in the output (large) |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
14 tool updates
- First observed
get_coverage - First observed
get_event - First observed
get_event_hotspots - First observed
get_event_trends - First observed
get_feature_details - First observed
get_fuel_prices - First observed
get_status - First observed
get_truck_corridor - First observed
list_feature_groups - First observed
list_feature_types - First observed
list_jurisdictions - First observed
plan_truck_route - First observed
search_events - First observed
search_features
Related MCP Connectors
US & Canada 511 road data: incidents, closures, cameras, truck restrictions. Paid API key.
141EV charging sites, plugs, tariffs, live status and history from European national access points.
European maps, geocoding and routing: places, routes, travel times, reachable areas and maps.
Maps for agents: truck/ADR routing, geocoding, places, matrices, isochrones, EV and fleet planning.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAI-powered route optimization MCP server for heavy vehicles and logistics. Calculate truck-optimized routes, predict traffic congestion with LSTM neural networks, compute toll costs, fuel costs and CO2 emissions, find truck stops and check weather along any European route.MIT
- FlicenseNot gradedqualityBmaintenanceEnables LLMs to access open real-time data from the Norwegian Public Roads Administration via DATEX II, including weather measurements and forecasts, webcams, travel times, and traffic messages.-
- AlicenseAqualityCmaintenanceProvides access to real-time Danish road traffic events, roadworks, and queues via public data from Vejdirektoratet, enabling AI assistants to check road conditions without any API keys.3MIT
- AlicenseAqualityCmaintenanceProvides real-time access to Swedish road weather, traffic cameras, road conditions, and traffic flow data from Trafikverket (Swedish Transport Administration). Enables users to query weather stations, cameras, traffic situations, and flow data through natural language.10MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.