Road511
REMOTE · API.ROAD511.COM
US & Canada 511 road data: incidents, closures, cameras, truck restrictions. Paid API key.
Available components
Last scanned (1 day ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1329 tokens (~94/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 10 Nov 26 +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.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 76
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.road511.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=road511.com | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b4660ec19b8ae03d81e07d351d5fbf0b86 |
| SANs: *.road511.com, road511.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.road511.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| road511.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.road511.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.road511.com/api/v1/mcp | HTTPS enforced | 301 | https://api.road511.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_coverage ~36
Per-jurisdiction counts of what data is available, by type.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | jurisdiction code; omit for all |
No output schema declared.
No examples provided.
get_event ~45
Full detail of one traffic event by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the id from a search result |
| include_geometry | boolean | – | keep geometry in the output (large) |
No output schema declared.
No examples provided.
get_event_hotspots ~66
Geographic clusters of traffic events. Needs a plan with analytics.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO 8601 lower bound |
| jurisdiction | string | – | jurisdiction code |
| to | string | – | ISO 8601 upper bound |
| type | string | – | event type |
No output schema declared.
No examples provided.
get_event_trends ~100
Event counts over time. Needs a plan with analytics.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_feature_details ~55
Full detail of one feature by id (for cameras, the current image/stream URLs).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the id from a search result |
| include_geometry | boolean | – | keep geometry in the output (large) |
No output schema declared.
No examples provided.
get_fuel_prices ~117
Fuel price series by jurisdiction, country and fuel type.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_status ~16
Service status: tracked resources and availability.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_truck_corridor ~122
Truck-relevant restrictions, clearances and events along a straight corridor between two points. Needs a plan with truck data.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_km | null|number | – | corridor half-width in km |
| from_lat | number | yes | origin latitude |
| from_lng | number | yes | origin longitude |
| jurisdiction | string | – | restrict to one jurisdiction |
| limit | integer | – | results to return, default 25, max 100 |
| to_lat | number | yes | destination latitude |
| to_lng | number | yes | destination longitude |
No output schema declared.
No examples provided.
list_feature_groups ~20
List feature groups, for search_features' group filter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_feature_types ~27
List feature types (cameras, weather stations, truck parking, restrictions...) with counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jurisdictions ~45
List the jurisdictions (states, provinces, countries, regions) with their codes.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | optional scope filter as accepted by GET /jurisdictions |
No output schema declared.
No examples provided.
plan_truck_route ~143
Compute a truck route with hazard warnings along it. Each call counts against the plan's monthly routing quota.
| Name | Type | Req | Description |
|---|---|---|---|
| departure_time | string | – | ISO 8601 or now |
| destination | object | yes | end point |
| include_geometry | boolean | – | keep the route polyline in the output (large) |
| origin | object | yes | start 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 {} |
| units | string | – | metric or imperial |
| waypoints | null|array | – | intermediate stops |
No output schema declared.
No examples provided.
search_events ~249
Search traffic events (incidents, construction, closures) by jurisdiction, area, type and time.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
search_features ~220
Search road features (cameras, weather stations, signs, truck parking, bridge clearances, restrictions...). Page with cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
How do I install the Road511 MCP server?
Road511 is a hosted endpoint at https://api.road511.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.
remote · api.road511.com
claude mcp add --transport http com-road511-traffic 'https://api.road511.com/api/v1/mcp'
What is the Road511 MCP server?
Road511 is an MCP server listed in the public MCP registry as com.road511/traffic. US & Canada 511 road data: incidents, closures, cameras, truck restrictions. Paid API key. This page covers its hosted endpoint (https://api.road511.com/api/v1/mcp).
Is the Road511 MCP server safe to use?
Road511 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 Road511 MCP server expose?
Road511 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 Road511 MCP server require authentication?
Yes. Road511 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 Road511 MCP server still maintained?
Road511 is still listed as active in the MCP registry. We last reached this channel on 21 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 Road511 MCP server?
VerifyMCP ran 13 checks on Road511, 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.