NHTSA Vehicle Safety MCP server

• complaint_trends_by_componentFree

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

• decode_vinFree

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

• get_complaintsFree

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

• get_crash_statisticsFree

  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.

• get_recallsFree

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

• local_vehicle_safety_profileFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 71ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

69/100

higher than 32% of 48,243 servers

Tools

6

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

105 ms

faster than 83% of 30,027 servers

NHTSA Vehicle Safety: common questions

Is NHTSA Vehicle Safety MCP server safe?

With care: it is graded C, so read the findings first (69/100). Read the NHTSA Vehicle Safety safety report

How do I install NHTSA Vehicle Safety?

It runs remotely at mcp.olyport.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does NHTSA Vehicle Safety need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is NHTSA Vehicle Safety maintained?

The latest release is v1.1.0.

Is NHTSA Vehicle Safety up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does NHTSA Vehicle Safety compare with other MCP servers?

safety score 69/100 (higher than 32% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.