
Wraps the NHTSA vPIC API so you can query vehicle product information without dealing with authentication or manual API calls. Exposes two main tools: get_makes pulls all vehicle brands for a given model year, and get_models returns vehicle models filtered by make and year. Useful when you're building features that need automotive reference data, like VIN decoders, vehicle comparison tools, or recall lookup systems. Part of the Pipeworx gateway, which means you can either use it standalone or access it alongside 250+ other data sources through a single MCP connection. The API itself is free and requires no auth, so there's no credential juggling.
The U.S. Department of Transportation's NHTSA. Vehicle recalls, complaints, investigations, crash test ratings (NCAP), safety standards, VIN decoder. The authoritative source for "is this car safe?" Free, no auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
For automotive research — buying a used car, evaluating recall exposure, analyzing fleet safety, doing IP / patent due diligence on vehicle technology — NHTSA is the canonical source. Pair with USPTO patents for vehicle-tech IP and Federal Register for proposed automotive rules.
Common flows:
None. NHTSA's APIs are fully public, free.
| Dataset | What it is |
|---|---|
| Recalls | Manufacturer recalls + investigations |
| Complaints | Consumer complaints by VIN/make/model |
| Investigations | Open NHTSA defect investigations |
| NCAP Crash Test | Star ratings, frontal/side/rollover scores |
| VIN Decoder | Decode VIN to make/model/year + manufacturer specs |
| TSBs (Technical Service Bulletins) | Manufacturer service guidance |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"nhtsa": {
"url": "https://gateway.pipeworx.io/nhtsa/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/nhtsa/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Nhtsa data" })
The gateway picks the right tool and fills the arguments automatically.
MIT