NHTSA Vehicle Safety MCP Server

by olyport Your server? Claim it

answering

NHTSA Vehicle Safety is answering right now. Last checked 6 min ago. It exposes 6 tools.

Vehicle safety recalls, complaints, and crash data from NHTSA

Uptime history 91 days of history

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

532 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check NHTSA Vehicle Safety 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 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

https://mcp.olyport.com/nhtsa/mcp

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "nhtsa": {
      "url": "https://mcp.olyport.com/nhtsa/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "nhtsa": {
      "type": "http",
      "url": "https://mcp.olyport.com/nhtsa/mcp"
    }
  }
}

Available tools 6

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

complaint

complaint_trends_by_component

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

complaints

get_complaints

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

crash

get_crash_statistics

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.

decode

decode_vin

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

local

local_vehicle_safety_profile

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.

recalls

get_recalls

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

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.olyport.com/nhtsa/mcp	streamable-http	answering	529 ms	6 min ago

Alternatives to NHTSA Vehicle Safety

same job, measured the same way

US Vehicle Recalls & VIN Check MCP

by donniertf-hub

Decode any VIN and see NHTSA safety recalls and owner complaints.

3 tools answering

Car Recalls MCP

by mrfentmen

Vehicle safety recalls from NHTSA by make, model, and year. No key required.

118 installs/wk local only

Nhtsa MCP

by mrfentmen

NHTSA: VIN decoding, safety recalls, owner complaints, make and model catalogues — keyless.

546 installs/wk local only

Carvector MCP

by carvectorio

Vehicle specs, federal recalls, complaints, TSBs, investigations and OBD-II DTC data for AI agents.

64 installs/wk local only

Vin Recall MCP

by pratikmehkarkar

Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.

2 tools answering

RecallChecker — Vehicle Safety Recalls

by checkrecall

Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.

1 tools answering

The Used Car Index

by theusedcarindex

Free NHTSA recalls, complaints and investigations per vehicle, recall alerts, dealer listing events.

4 tools answering

Nhtsa Vehicle Safety MCP Server

by cyanheads

Decode VINs, search recalls, complaints, crash ratings, and investigations.

256 installs/wk 7 tools answering

NHTSA Vehicle Safety — questions

Answers built from our own checks of this server.

What can NHTSA Vehicle Safety do?

It exposes 6 tools, read directly from the server on our last check. Among them: complaint_trends_by_component, decode_vin, get_complaints, get_crash_statistics, get_recalls, local_vehicle_safety_profile. 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 →

Is NHTSA Vehicle Safety working right now?

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

How do I connect NHTSA Vehicle Safety?

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 NHTSA Vehicle Safety need an API key?

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

How fast is NHTSA Vehicle Safety?

It answers our handshake in 532 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.