# NHTSA Vehicle Safety (remote · mcp.olyport.com)

Vehicle safety recalls, complaints, and crash data from NHTSA

- Trust score: 65/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.olyport.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp.md), [page](https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp)

## Channel facts

- Endpoint: `https://mcp.olyport.com/nhtsa/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-olyport-nhtsa https://mcp.olyport.com/nhtsa/mcp
```

### Codex

```toml
[mcp_servers.com-olyport-nhtsa]
url = "https://mcp.olyport.com/nhtsa/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-olyport-nhtsa": {
      "type": "remote",
      "url": "https://mcp.olyport.com/nhtsa/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-olyport-nhtsa --url https://mcp.olyport.com/nhtsa/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-olyport-nhtsa:
    url: "https://mcp.olyport.com/nhtsa/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 65, +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.

### 2026-07-31 (score 64, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +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.

### 2026-07-28 (score 60, +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.

### 2026-07-27 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (6)

### `decode_vin` (~88 tokens)

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').

Input parameters:

- `vin` (string, required)

Output parameters:

- `result` (string)

### `get_recalls` (~144 tokens)

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).

Input parameters:

- `make` (string)
- `model` (string)
- `year` (integer)

Output parameters:

- `result` (string)

### `get_complaints` (~161 tokens)

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).

Input parameters:

- `limit` (integer)
- `make` (string)
- `model` (string)
- `year` (integer)

Output parameters:

- `result` (string)

### `get_crash_statistics` (~144 tokens)

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.

Input parameters:

- `state` (string, required)
- `year` (integer)

Output parameters:

- `result` (string)

### `complaint_trends_by_component` (~133 tokens)

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).

Input parameters:

- `make` (string, required)
- `model` (string, required)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `local_vehicle_safety_profile` (~106 tokens)

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.

Input parameters:

- `state` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 61
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.olyport.com/nhtsa/mcp
- Website: https://olyport.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-olyport-nhtsa/nhtsa-mcp