Vehicle safety data from NHTSA — recalls, complaints, crash ratings, investigations, VIN decoding.
Most file and storage access work still happens through a UI a human drives. Nhtsa MCP server moves it into the conversation instead. Vehicle safety data from NHTSA — recalls, complaints, crash ratings, investigations, VIN decoding.
The server publishes 10 tools. What each one is for:
nhtsa_get_vehicle_safety — Comprehensive safety profile combining crash test ratings, recalls, and complaint summary with per-section availability statusnhtsa_search_recalls — Search recall campaigns by vehicle or campaign number with optional date filteringnhtsa_search_complaints — Consumer safety complaints with component breakdown and severity statsnhtsa_get_safety_ratings — NCAP crash test ratings and ADAS feature availabilitynhtsa_decode_vin — Decode VINs for make, model, year, engine, safety equipment (single or batch up to 50)nhtsa_search_investigations — Search NHTSA defect investigations (PE, EA, DP, RQ, AQ, and more) with cached indexnhtsa_lookup_vehicles — Look up valid makes, models, vehicle types, and manufacturer details from VPICPrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverProduction — The Production tool exposed by this serverConfiguration is passed through the environment: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, MCP_HTTP_HOST, MCP_HTTP_ENDPOINT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nhtsa's toolset — nhtsa_get_vehicle_safety, nhtsa_search_recalls, nhtsa_search_complaints and 7 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| nhtsa_get_vehicle_safety | Comprehensive safety profile combining crash test ratings, recalls, and complaint summary with per-section availability status. |
| nhtsa_search_recalls | Search recall campaigns by vehicle or campaign number with optional date filtering. |
| nhtsa_search_complaints | Consumer safety complaints with component breakdown and severity stats. |
| nhtsa_get_safety_ratings | NCAP crash test ratings and ADAS feature availability. |
| nhtsa_decode_vin | Decode VINs for make, model, year, engine, safety equipment (single or batch up to 50). |
| nhtsa_search_investigations | Search NHTSA defect investigations (PE, EA, DP, RQ, AQ, and more) with cached index. |
| nhtsa_lookup_vehicles | Look up valid makes, models, vehicle types, and manufacturer details from VPIC. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Production | The Production tool exposed by this server. |
{
"mcpServers": {
"nhtsa-vehicle-safety-mcp-server": {
"type": "streamable-http",
"url": "https://nhtsa.caseyjhand.com/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Configuration value read at startup. | Optional |
| MCP_LOG_LEVEL | Configuration value read at startup. | Optional |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_HTTP_ENDPOINT_PATH | Filesystem location the server is allowed to use. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.