Gives Claude a single tool to check U.S. vehicle safety recalls by calling the NHTSA Recalls API with make, model, and year. Returns plain language summaries with campaign numbers, hazard descriptions, remedy info, and links to official notices. The same lookup logic powers both the MCP server and the public web tool at checkrecall.com, so results are consistent across interfaces. Useful when you need to answer "is this car recalled" during research, customer support flows, or any conversation where someone mentions a specific vehicle. No API key required since it wraps a public NHTSA endpoint. Data is cached on Cloudflare Workers KV to keep responses fast.
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
/recalls/[make]/[model]/[year],
each backed by live data.check_vehicle_recalls(make, model, year), returning a human-readable summary plus
structured data.| 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).
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.
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).
MIT — see LICENSE.
makafeli/n8n-workflow-builder
danishashko/make-mcp
lukisch/n8n-manager-mcp
io.github.us-all/airflow
io.github.infoinlet-marketplace/mcp-workflow