RecallChecker
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RecallCheckerCheck recalls for 2021 Ford F-150"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RecallChecker
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.
Related MCP server: VIN MCP
Data source
Source | Provides | Notes |
NHTSA Recalls API | U.S. vehicle safety recall campaigns | No API key. |
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 serverBuild uses
next build --webpack(Turbopack output is not yet compatible with OpenNext).
License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ollo12-prog/recallchecker'
If you have feedback or need assistance with the MCP directory API, please join our Discord server