U.S. CPSC/NHTSA recall status with agency links and a signed receipt.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Checks U.S. government recall records and returns the status with the agency's own links and a signed receipt. Give `product` (a name, matched against CPSC recall titles) or `vehicle` (model year, make, model, looked up at NHTSA). Returns status recalls_found with the newest recalls (id, title, date, summary, hazard, remedy, link) or none_found; confidence says how far to trust the search (CPSC matches title words; NHTSA is exact per model). Confidence unknown when the agency's answer could not be read. Call it before advising on a used product or vehicle, or when asked whether something has been recalled.
Products only: ignore CPSC recalls announced before this date (YYYY-MM-DD). Narrows the list; it does not make a slow CPSC search faster.
Consumer product to check with the U.S. CPSC. Words matched against recall titles, which read like "Peloton Recalls Tread+ Treadmills", so use the brand or the product name, not both: "Tread+" or "Rock 'n Play". Fewer words match more. Give either product or vehicle, not both.
Vehicle to check with the U.S. NHTSA by model year, make and model. Give either product or vehicle, not both.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http recall-check https://recalls.bot2botlabs.com/mcp
Checks U.S. government recall records and returns the status with the agency's own links and a signed receipt. Give `product` (a name, matched against CPSC recall titles) or `vehicle` (model year, make, model, looked up at NHTSA). Returns status recalls_found with the newest recalls (id, title, date, summary, hazard, remedy, link) or none_found; confidence says how far to trust the search (CPSC matches title words; NHTSA is exact per model). Confidence unknown when the agency's answer could not be read. Call it before advising on a used product or vehicle, or when asked whether something has been recalled.
| Argument | Type | Description |
|---|---|---|
| since | string | Products only: ignore CPSC recalls announced before this date (YYYY-MM-DD). Narrows the list; it does not make a slow CPSC search faster. |
| product | string | Consumer product to check with the U.S. CPSC. Words matched against recall titles, which read like "Peloton Recalls Tread+ Treadmills", so use the brand or the product name, not both: "Tread+" or "Rock 'n Play". Fewer words match more. Give either product or vehicle, not both. |
| vehicle | object | Vehicle to check with the U.S. NHTSA by model year, make and model. Give either product or vehicle, not both. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"since": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Products only: ignore CPSC recalls announced before this date (YYYY-MM-DD). Narrows the list; it does not make a slow CPSC search faster."
},
"product": {
"type": "string",
"maxLength": 120,
"minLength": 2,
"description": "Consumer product to check with the U.S. CPSC. Words matched against recall titles, which read like \"Peloton Recalls Tread+ Treadmills\", so use the brand or the product name, not both: \"Tread+\" or \"Rock 'n Play\". Fewer words match more. Give either product or vehicle, not both."
},
"vehicle": {
"type": "object",
"required": [
"make",
"model",
"year"
],
"properties": {
"make": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "e.g. \"Toyota\""
},
"year": {
"type": "integer",
"maximum": 2028,
"minimum": 1949,
"description": "Model year, 1949 to 2028"
},
"model": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "e.g. \"Camry\" or \"Grand Cherokee\"; must be the model name as NHTSA lists it"
}
},
"description": "Vehicle to check with the U.S. NHTSA by model year, make and model. Give either product or vehicle, not both.",
"additionalProperties": false
}
},
"additionalProperties": false
}Fetch a receipt issued by check_recall (format v1, signed, software-only TRACE record). The same document is served at https://recalls.bot2botlabs.com/receipts/{receipt_id}.
| Argument | Type | Description |
|---|---|---|
| receipt_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"receipt_id"
],
"properties": {
"receipt_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 13, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.