Pet food recalls from US, UK, Canadian and French registers, kept after removal.
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.
Ask in plain language about a brand, product, barcode, lot code, country or reason ("Has Purina been recalled in the UK?", "salmonella recalls in France in 2025"). Returns a short answer written only from the matching official notices, with numbered sources (URL, date, country, brand, product, reason, lot codes, barcodes, official notice). Coverage is the US, UK, Canada and France. A question with no match is not evidence that a product is safe; say so.
The question, in any wording. Up to 300 characters.
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 recalls https://pawmultiverse.com/mcp-recalls
Ask in plain language about a brand, product, barcode, lot code, country or reason ("Has Purina been recalled in the UK?", "salmonella recalls in France in 2025"). Returns a short answer written only from the matching official notices, with numbered sources (URL, date, country, brand, product, reason, lot codes, barcodes, official notice). Coverage is the US, UK, Canada and France. A question with no match is not evidence that a product is safe; say so.
| Argument | Type | Description |
|---|---|---|
| question* | string | The question, in any wording. Up to 300 characters. |
{
"type": "object",
"required": [
"question"
],
"properties": {
"question": {
"type": "string",
"description": "The question, in any wording. Up to 300 characters."
}
}
}Given the barcode printed on a bag, tin or pouch of pet food (EAN, UPC or GTIN), return every recall notice held against that barcode across all of the registers this record covers, in one answer. Also returns how much of each country register is held, so that finding nothing can be reported honestly. IMPORTANT: no match does NOT mean the product is safe. It means no authority whose register is listed here has published a recall carrying that barcode in what has been read so far. Say that, and do not translate it into a reassurance. Many recalls are announced by lot or best-before date rather than by barcode, so a matching bag can still be affected; when a match is returned, check the lot and best-before codes on the notice against the ones on the bag before drawing a conclusion.
| Argument | Type | Description |
|---|---|---|
| code* | string | The barcode as printed, digits only. EAN-13, UPC-A or GTIN. |
{
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "The barcode as printed, digits only. EAN-13, UPC-A or GTIN."
}
}
}Return the products that appear in more than one country register, matched on barcode: the same item recalled by two or more authorities. This view exists nowhere else, including at the authorities themselves, each of which publishes only its own country. Use it to answer whether a recall in one country has a counterpart elsewhere. A product appearing in only one country here has not been shown to be safe in the others; it has only not been matched.
No arguments.
{
"type": "object",
"properties": {}
}Return one entry from the record in full: what the authority published, the firm, the product, the reason given, the lot and best-before codes where they were published, and every dated version held, so that a change the authority made to its own notice is visible. Also returns whether the entry is still listed on the authority site or has been removed from it, and the date it was last seen. Identify the entry either by its id (the "source:key" string returned by the other tools) or by source and key separately.
| Argument | Type | Description |
|---|---|---|
| id | string | The record id in the form source:key, for example us-fda-animal-recalls:2026-09-08-db4bc500. |
| on | string | Optional date, YYYY-MM-DD. Read the entry as it stood on that date rather than as it stands now. |
| key | string | The key within that register, if giving source and key separately. |
| source | string | The register slug, if giving source and key separately. |
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The record id in the form source:key, for example us-fda-animal-recalls:2026-09-08-db4bc500."
},
"on": {
"type": "string",
"description": "Optional date, YYYY-MM-DD. Read the entry as it stood on that date rather than as it stands now."
},
"key": {
"type": "string",
"description": "The key within that register, if giving source and key separately."
},
"source": {
"type": "string",
"description": "The register slug, if giving source and key separately."
}
}
}Return every official register this record reads, with the authority that publishes it, its licence, how many entries are held from it, how often it is read, and the last time it was read without error. Use this before quoting the record to establish how current it is, and to tell someone which countries are covered and which are not. A country that is not listed here is not covered, and nothing should be inferred about it.
No arguments.
{
"type": "object",
"properties": {}
}Keyword search over every recall held, without any AI writing. Returns up to 20 matching notices with their permanent URLs and key facts, newest and best matches first. Filter by country (us, gb, ca, fr) and year.
| Argument | Type | Description |
|---|---|---|
| year | string | Optional: four-digit year of the notice. |
| query | string | Brand, company, product words, reason (for example salmonella), lot code or barcode. |
| country | string | Optional: us, gb, ca or fr. |
{
"type": "object",
"properties": {
"year": {
"type": "string",
"description": "Optional: four-digit year of the notice."
},
"query": {
"type": "string",
"description": "Brand, company, product words, reason (for example salmonella), lot code or barcode."
},
"country": {
"type": "string",
"description": "Optional: us, gb, ca or fr."
}
}
}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 11, 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.