NHTSA Vehicle Safety
REMOTE · MCP.OLYPORT.COM · SCANNED AUG 3
Vehicle safety recalls, complaints, and crash data from NHTSA
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 776 tokens (~129/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.olyport.com
claude mcp add --transport http com-olyport-nhtsa https://mcp.olyport.com/nhtsa/mcp
[mcp_servers.com-olyport-nhtsa] url = "https://mcp.olyport.com/nhtsa/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-olyport-nhtsa": {
"type": "remote",
"url": "https://mcp.olyport.com/nhtsa/mcp",
"enabled": true
}
}
} openclaw mcp add com-olyport-nhtsa --url https://mcp.olyport.com/nhtsa/mcp --transport streamable-http
mcp_servers:
com-olyport-nhtsa:
url: "https://mcp.olyport.com/nhtsa/mcp" {
"mcpServers": {
"com-olyport-nhtsa": {
"type": "http",
"url": "https://mcp.olyport.com/nhtsa/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
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 3 Aug 2026 · Probed https://mcp.olyport.com/nhtsa/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.olyport.com | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6ab1c2dfb0fcb68c1046393bb51c5b1117b |
| SANs: mcp.olyport.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 |
DNSSEC insecure
Validation of mcp.olyport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| olyport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.olyport.com/nhtsa/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.olyport.com/nhtsa/mcp | HTTPS enforced | 308 | https://mcp.olyport.com/nhtsa/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.
complaint_trends_by_component ~133
Get complaint counts by vehicle component for a specific make/model/year. Shows which parts of the vehicle consumers report the most problems with (e.g. brakes, engine, electrical system). Useful for identifying systemic vehicle defect patterns. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford'). model: Vehicle model name (e.g. 'Camry', 'F-150'). year: Model year (e.g. 2023).
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | — |
| model | string | yes | — |
| year | integer | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
decode_vin ~88
Decode a Vehicle Identification Number (VIN) to get vehicle details. Returns make, model, year, body class, engine info, safety features, and other attributes encoded in the 17-character VIN. Args: vin: A 17-character Vehicle Identification Number (e.g. '1HGBH41JXMN109186').
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_complaints ~161
Get consumer complaints about vehicles filed with NHTSA. Search for safety complaints by make, model, and/or year. Returns complaint descriptions, components involved, and crash/injury data. At least one filter (make, model, or year) should be provided. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford'). model: Vehicle model name (e.g. 'Camry', 'F-150'). year: Model year (e.g. 2023). limit: Maximum number of complaints to return (default 25).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| make | string | — | — |
| model | string | — | — |
| year | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_crash_statistics ~144
Get fatal crash statistics from the NHTSA Fatality Analysis Reporting System (FARS). Returns fatal motor vehicle crash data for a state, including total fatalities, fatalities by person type (drivers, passengers, pedestrians), and alcohol-involved crashes. Args: state: Two-digit state FIPS code (e.g. '06' for California, '48' for Texas) or two-letter state abbreviation (e.g. 'CA', 'TX'). year: Year for statistics (e.g. 2022). Defaults to the most recent available year.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | — |
| year | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_recalls ~144
Get vehicle safety recalls from NHTSA. Search for recalls by make, model, and/or year. Returns recall campaigns including the defect description, remedy, and affected vehicles. At least one filter (make, model, or year) should be provided. Args: make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford', 'Honda'). model: Vehicle model name (e.g. 'Camry', 'F-150', 'Civic'). year: Model year (e.g. 2023).
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | — | — |
| model | string | — | — |
| year | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
local_vehicle_safety_profile ~106
Get a vehicle safety profile using national complaint and recall trends. NHTSA complaints are not geocoded by state, so this returns national-level trends as context for local community safety assessments. Includes the most recent recalls and top complained-about vehicle makes. Args: state: Two-letter state abbreviation (e.g. 'CA', 'TX'). Used for crash statistics; complaint data is national.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.