NAPSPAN MCP Server

by napspan Your server? Claim it

answering

NAPSPAN is answering right now. Last checked 12 min ago. It exposes 14 tools.

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

Uptime history 21 hours of history

21 hours agonow

100.0%

Uptime 24h

78 of 78 checks

Tools

read from the server

167 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check NAPSPAN every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add traffic --transport http https://api.napspan.com/api/v1/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.napspan.com/api/v1/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

event

get_event

Full detail of one traffic event by id.

get_event_hotspots

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

get_event_trends

Event counts over time. Needs a plan with analytics.

feature

get_feature_details

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

list_feature_groups

List feature groups, for search_features' group filter.

list_feature_types

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

coverage

get_coverage

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

events

search_events

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

features

search_features

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

fuel

get_fuel_prices

Fuel price series by jurisdiction, country and fuel type.

jurisdictions

list_jurisdictions

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

plan

plan_truck_route

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

status

get_status

Service status: tracked resources and availability.

truck

get_truck_corridor

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

Endpoints

URL	Transport	State	Latency	Checked
https://api.napspan.com/api/v1/mcp	streamable-http	answering	166 ms	12 min ago

Alternatives to NAPSPAN

same job, measured the same way

Road511

by road511

US & Canada 511 road data: incidents, closures, cameras, truck restrictions. Paid API key.

14 tools answering

Statuspage Incidents

by fly-looper-products

Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.

1 tools answering

Vendor Status MCP

by approj

Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.

local only

NIFC Wildfire Data

by olyport

Active wildfire incidents from the National Interagency Fire Center

3 tools answering

WebUpCheck — DNS, Website & Provider Diagnostics

by webupcheck

DNS comparison, Claude and cloud components/incidents, and website diagnostics. Free; no API key.

7 tools answering

BetterStack Status Page Scraper & API Tool

by ranovam

Get any company's BetterStack (Better Uptime) status page as clean JSON — components, incidents…

answering

National Parks MCP Server

by cyanheads

Plan US National Park Service trips — parks, alerts, campgrounds, things to do, events.

133 installs/wk 6 tools answering

Statuspage MCP

by mrfentmen

Query Statuspage management API: pages, page details, incidents.

75 installs/wk local only

NAPSPAN — questions

Answers built from our own checks of this server.

What can NAPSPAN do?

It exposes 14 tools, read directly from the server on our last check. Among them: get_coverage, get_event, get_event_hotspots, get_event_trends, get_feature_details, get_fuel_prices and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is NAPSPAN mostly used for?

Its tools cluster around event and feature. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is NAPSPAN working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 78 of 78 checks got a reply (100.0%), average response time 167 ms. The bar chart above shows every period we have measured.

How do I connect NAPSPAN?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does NAPSPAN need an API key?

No. NAPSPAN completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is NAPSPAN?

It answers our handshake in 167 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.