Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
NAPSPAN is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
European NAP road data (DATEX II): incidents, roadworks, cameras, truck parking. Paid API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http napspan-mcp https://api.napspan.com/api/v1/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# get_coverage, get_event, get_event_hotspots and 11 more
It needs AUTHORIZATION (Bearer <your NAPSPAN API key> - sign up at https://portal.napspan.com/signup (free trial, then a paid plan)): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
NAPSPAN costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NAAll 1 server
napspan1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer <your NAPSPAN API key> - sign up at https://portal.napspan.com/signup (free trial, then a paid plan)) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http napspan-mcp https://api.napspan.com/api/v1/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer <your NAPSPAN API key> - sign up at https://portal.napspan.com/signup (free trial, then a paid plan). You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Per-jurisdiction counts of what data is available, by type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction code; omit for all |
Full detail of one traffic event by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | the id from a search result |
| include_geometry | boolean | no | keep geometry in the output (large) |
Geographic clusters of traffic events. Needs a plan with analytics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction code |
| type | string | no | event type |
| from | string | no | ISO 8601 lower bound |
| to | string | no | ISO 8601 upper bound |
Event counts over time. Needs a plan with analytics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction code |
| type | string | no | event type |
| from | string | no | ISO 8601 lower bound |
| to | string | no | ISO 8601 upper bound |
| severity | string | no | severity filter |
| bucket | string | no | time bucket, e.g. day or week |
| group_by | string | no | grouping dimension |
Full detail of one feature by id (for cameras, the current image/stream URLs).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | the id from a search result |
| include_geometry | boolean | no | keep geometry in the output (large) |
Fuel price series by jurisdiction, country and fuel type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction or region code |
| country | string | no | country code |
| fuel_type | string | no | fuel type, e.g. diesel |
| latest | null/boolean | no | only the latest price per series |
| from | string | no | ISO 8601 date lower bound |
| to | string | no | ISO 8601 date upper bound |
| limit | integer | no | results to return, default 25, max 100 |
Service status: tracked resources and availability.
No parameter schema on file.
Truck-relevant restrictions, clearances and events along a straight corridor between two points. Needs a plan with truck data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_lat | number | yes | origin latitude |
| from_lng | number | yes | origin longitude |
| to_lat | number | yes | destination latitude |
| to_lng | number | yes | destination longitude |
| buffer_km | null/number | no | corridor half-width in km |
| jurisdiction | string | no | restrict to one jurisdiction |
| limit | integer | no | results to return, default 25, max 100 |
List feature groups, for search_features' group filter.
No parameter schema on file.
List feature types (cameras, weather stations, truck parking, restrictions...) with counts.
No parameter schema on file.
List the jurisdictions (states, provinces, countries, regions) with their codes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | optional scope filter as accepted by GET /jurisdictions |
Compute a truck route with hazard warnings along it. Each call counts against the plan's monthly routing quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | object | yes | start point |
| destination | object | yes | end point |
| truck | object | yes | truck profile as in POST /routing/route, e.g. {"weight_t":36,"height_m":4.1,"length_m":21}; may be {} |
| waypoints | null/array | no | intermediate stops |
| departure_time | string | no | ISO 8601 or now |
| units | string | no | metric or imperial |
| include_geometry | boolean | no | keep the route polyline in the output (large) |
Search traffic events (incidents, construction, closures) by jurisdiction, area, type and time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction code, comma-separated for several |
| bbox | string | no | bounding box min_lng,min_lat,max_lng,max_lat |
| lat | null/number | no | centre latitude for a radius search (with lng and radius_km) |
| lng | null/number | no | centre longitude for a radius search |
| radius_km | null/number | no | search radius in km |
| type | string | no | event type, e.g. incident, construction, closure |
| severity | string | no | severity filter |
| status | string | no | status filter, e.g. active |
| road | string | no | road name or number filter |
| start_time_from | string | no | ISO 8601 lower bound on start time |
| start_time_to | string | no | ISO 8601 upper bound on start time |
| limit | integer | no | results to return, default 25, max 100 |
| offset | integer | no | results to skip for the next page |
| include_geometry | boolean | no | keep geometry in the output (large) |
Search road features (cameras, weather stations, signs, truck parking, bridge clearances, restrictions...). Page with cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | jurisdiction code, comma-separated for several |
| bbox | string | no | bounding box min_lng,min_lat,max_lng,max_lat |
| lat | null/number | no | centre latitude for a radius search (with lng and radius_km) |
| lng | null/number | no | centre longitude for a radius search |
| radius_km | null/number | no | search radius in km |
| type | string | no | feature type from list_feature_types, e.g. cameras, truck_parking, bridge_clearances |
| group | string | no | feature group id from list_feature_groups |
| active | null/boolean | no | only active features (default true upstream) |
| limit | integer | no | results to return, default 25, max 100 |
| cursor | string | no | next_cursor from the previous page |
| include_geometry | boolean | no | keep geometry in the output (large) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NAPSPAN or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 9 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest9c02778a1cbf5535055e6ac4554afbe794503323d4c7dd6474e64d59f13dd39f
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_coverage | no tags | |
| get_event | no tags | |
| get_event_hotspots | no tags | |
| get_event_trends | no tags | |
| get_feature_details | no tags | |
| get_fuel_prices | no tags | |
| get_status | no tags | |
| get_truck_corridor | no tags | |
| list_feature_groups | no tags | |
| list_feature_types | no tags | |
| list_jurisdictions | no tags | |
| plan_truck_route | no tags | |
| search_events | no tags | |
| search_features | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9c02778a1cbf5535
Scanned2026-11-09
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NAPSPAN can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.