mcp server
NHTSA Vehicle Safety
Vehicle safety recalls, complaints, and crash data from NHTSA
Description as published by the maintainer. Source
- version 1.1.0
- slowing
- memory and context
slowing — Registry entry last updated 2026-04-02. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
complaint_trends_by_component(make, year, model)- 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). Required: make, model, year.
decode_vin(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'). Required: vin.
get_complaints(make, year, limit, model)- 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_statistics(year, state)- 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. Required: state.
get_recalls(make, year, model)- 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_profile(state)- 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. Required: state.
Last successful function declaration observed on . Source: https://mcp.olyport.com/nhtsa/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.olyport.com/nhtsa/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.olyport.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | mcp.olyport.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json