RecallChecker — Vehicle Safety Recalls
RemoteAbout RecallChecker — Vehicle Safety Recalls
RecallChecker is a web tool and MCP server that checks open U.S. vehicle safety recalls using live NHTSA data. It is for people checking a vehicle by make, model, and year, and returns plain-language details with official notices; results are not VIN-specific.
Key features
- 01Look up recalls by make, model, and year
- 02Show hazards, remedies, and campaign dates
- 03Link to official NHTSA notices
- 04Return human-readable and structured results
- 05Display the data's as-of date
Use cases
- 01Check open recalls before buying a used vehicle
- 02Review recall remedies for a particular model year
- 03Share a vehicle recall lookup result
MCP support
The MCP server exposes `check_vehicle_recalls(make, model, year)` to MCP clients, returning a human-readable summary and structured data sourced live from the NHTSA Recalls API.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.checkrecall.com/mcpclaude mcp add --transport http com-checkrecall-vehicle-recalls https://mcp.checkrecall.com/mcp{"mcpServers":{"com-checkrecall-vehicle-recalls":{"type":"http","url":"https://mcp.checkrecall.com/mcp"}}}Open in Cursor{"servers":{"com-checkrecall-vehicle-recalls":{"type":"http","url":"https://mcp.checkrecall.com/mcp"}}}Open in VS Code{"mcpServers":{"com-checkrecall-vehicle-recalls":{"type":"http","url":"https://mcp.checkrecall.com/mcp"}}}{"mcpServers":{"com-checkrecall-vehicle-recalls":{"serverUrl":"https://mcp.checkrecall.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
1| Parameter | Type | Required | Description |
|---|---|---|---|
| make | string | Yes | Vehicle make, e.g. Honda, Ford, Toyota |
| year | integer | Yes | Four-digit model year, e.g. 2021 |
| model | string | Yes | Vehicle model, e.g. Civic, F-150, Camry |
Details
From the project READMERecallChecker
A free tool + MCP server that answers one question well: "Is this vehicle recalled?" Enter a car's make, model, and year and get an instant, plain-language list of open U.S. safety recalls — pulled live from official NHTSA data, with the hazard, the remedy, the date, and a link to the official notice.
Live: checkrecall.com · MCP: https://mcp.checkrecall.com/mcp
Features
- Web tool — search by make / model / year and get a direct answer with the recall count, campaign details, dates, and official links. Results live at a shareable, crawlable URL.
- Reference pages — a page per common vehicle query at
/recalls/[make]/[model]/[year], each backed by live data. - MCP server — the same lookup as a tool any MCP-compatible AI assistant can call:
check_vehicle_recalls(make, model, year), returning a human-readable summary plus structured data.
Data source
| Source | Provides | Notes |
|---|---|---|
| NHTSA Recalls API | U.S. vehicle safety recall campaigns | No API key. api.nhtsa.gov/recalls/recallsByVehicle?make=&model=&modelYear= |
Every answer shows the data's "as of" date and links back to the official NHTSA notice. A "no recalls found" result reports the absence of campaigns in NHTSA as of that date — it is not a guarantee of safety and is not VIN-specific. Data sourced from NHTSA (nhtsa.gov).
Tech
Next.js (App Router) + TypeScript, deployed to Cloudflare Workers via OpenNext; response caching on Workers KV. The MCP server is a second Worker that reuses the same lookup core, so the website and the assistant tool never duplicate lookup logic.
Development
npm install
npm run dev # local dev (wrangler)
npm test # unit tests
npm run deploy # deploy the web app
npm run mcp:dev # local MCP server
npm run mcp:deploy # deploy the MCP server
Build uses
next build --webpack(Turbopack output is not yet compatible with OpenNext).
License
MIT — see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.