RecallChecker — Vehicle Safety Recalls MCP Server
com.checkrecall/vehicle-recalls
answering
RecallChecker — Vehicle Safety Recalls is answering right now. Last checked 12 min ago. It exposes 1 tools. Last commit 25 May 2026.
Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.
Uptime history
42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
177 ms
Response time
average over 24h
0
Stars
last commit 25 May 2026
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
run in your terminal
claude mcp add vehicle-recalls --transport http https://mcp.checkrecall.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"vehicle-recalls": {
"url": "https://mcp.checkrecall.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.vehicle-recalls]
url = "https://mcp.checkrecall.com/mcp".cursor/mcp.json
{
"mcpServers": {
"vehicle-recalls": {
"url": "https://mcp.checkrecall.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"vehicle-recalls": {
"url": "https://mcp.checkrecall.com/mcp"
}
}
}Available tools 1
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
vehicle
check_vehicle_recalls
Check U.S. NHTSA safety recall campaigns for a vehicle by make, model, and model year. Returns official NHTSA recall campaigns (component, hazard, remedy, campaign number, official notice link) plus the date the data was fetched. Results are model-year campaign matches, NOT VIN-specific repair status — an empty result means no open recalls were found in NHTSA as of the returned date, which is not a guarantee the vehicle is safe.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.checkrecall.com/mcp | streamable-http | answering | 219 ms | 12 min ago |
RecallChecker — Vehicle Safety Recalls — questions
Answers built from our own checks of this server.
What can RecallChecker — Vehicle Safety Recalls do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_vehicle_recalls. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is RecallChecker — Vehicle Safety Recalls working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 177 ms. The bar chart above shows every period we have measured.
How do I connect RecallChecker — Vehicle Safety Recalls?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does RecallChecker — Vehicle Safety Recalls need an API key?
No. RecallChecker — Vehicle Safety Recalls completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is RecallChecker — Vehicle Safety Recalls?
It answers our handshake in 177 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is RecallChecker — Vehicle Safety Recalls open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.