Nhtsa Vehicle Safety Mcp Server
Wire NHTSA VIN decode, recalls, complaints, and safety ratings into your agent so automotive or fleet side projects do not need custom government API glue.
Overview
io.github.cyanheads/nhtsa-vehicle-safety-mcp-server is a MCP server for the Build phase that decodes VINs and queries NHTSA recalls, complaints, crash ratings, and investigations from your agent.
What is this MCP server?
- Decodes VINs into make, model, and configuration context from federal data
- Searches recalls, consumer complaints, crash test ratings, and investigations
- Packages version 0.8.2 as @cyanheads/nhtsa-vehicle-safety-mcp-server
- Offers stdio, local streamable-http, and optional remote at nhtsa.caseyjhand.com/mcp
- Tunable MCP_LOG_LEVEL for integration debugging
- Published version 0.8.2 on npm as @cyanheads/nhtsa-vehicle-safety-mcp-server
- Documented remote MCP URL at nhtsa.caseyjhand.com/mcp
- Stdio and streamable-http transport options in server manifest
Community signal: 1 GitHub stars.
What problem does it solve?
Automotive side projects stall on scattered NHTSA endpoints and inconsistent parsing when you only want quick safety answers inside the IDE.
Who is it for?
Solo builders adding US vehicle safety checks to marketplaces, fleet tools, or AI support flows during active development.
Skip if: Products that need non-US regulatory data, real-time telematics, or OEM-private service histories without other integrations.
What do I get? / Deliverables
Registering this server gives your agent callable tools for federal vehicle safety data so features like recall alerts ship without a bespoke API layer.
- Agent-callable VIN decode and safety search tools
- Recall and complaint context for listing or support features
- Crash rating and investigation data for trust UX copy
Recommended MCP Servers
Journey fit
Once you are building, external compliance and vehicle data belong in integrations—this server standardizes US federal safety endpoints behind MCP tools. Integrations is the shelf for third-party APIs; NHTSA feeds are classic backend dependencies for marketplaces, garage apps, and insurance adjacency tools.
How it compares
NHTSA integration MCP server, not a VIN database vendor or dealership DMS replacement.
Common Questions / FAQ
Who is io.github.cyanheads/nhtsa-vehicle-safety-mcp-server for?
It is for developers using AI agents who build auto, fleet, or resale products and need standardized access to US NHTSA safety and identification data.
When should I use io.github.cyanheads/nhtsa-vehicle-safety-mcp-server?
Use it while building backend or agent features that must decode VINs or surface recalls and safety ratings without writing one-off HTTP clients.
How do I add io.github.cyanheads/nhtsa-vehicle-safety-mcp-server to my agent?
Add @cyanheads/nhtsa-vehicle-safety-mcp-server to MCP config, run the npm package start:stdio entry via Bun, or connect to the documented HTTP remote or localhost streamable-http endpoint.