Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Paw Multiverse pet food recalls

REMOTE · PAWMULTIVERSE.COM

Pet food recalls from US, UK, Canadian and French registers, kept after removal.

+3 this week 68 Trust /100

Last scanned (12 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1069 tokens (~178/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://pawmultiverse.com/mcp-recalls

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pawmultiverse.com CN=WE1,O=Google Trust Services,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA256 58446cffdb44973c0e2948f88b0f80bd
SANs: pawmultiverse.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pawmultiverse.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
pawmultiverse.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pawmultiverse.com/mcp-recalls Verified 200
http (plaintext) http://pawmultiverse.com/mcp-recalls HTTPS enforced 301 https://pawmultiverse.com/mcp-recalls
MCP tools · 6 exposed · ~861 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_recall_record ~134

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.

NameTypeReqDescription
questionstringyesThe question, in any wording. Up to 300 characters.

No output schema declared.

No examples provided.

check_pet_food_bag ~198

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.

NameTypeReqDescription
codestringyesThe barcode as printed, digits only. EAN-13, UPC-A or GTIN.

No output schema declared.

No examples provided.

cross_border_recalls ~98

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_recall_record ~220

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.

NameTypeReqDescription
idstring–The record id in the form source:key, for example us-fda-animal-recalls:2026-09-08-db4bc500.
keystring–The key within that register, if giving source and key separately.
onstring–Optional date, YYYY-MM-DD. Read the entry as it stood on that date rather than as it stands now.
sourcestring–The register slug, if giving source and key separately.

No output schema declared.

No examples provided.

list_recall_registers ~98

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_recalls ~113

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.

NameTypeReqDescription
countrystring–Optional: us, gb, ca or fr.
querystring–Brand, company, product words, reason (for example salmonella), lot code or barcode.
yearstring–Optional: four-digit year of the notice.

No output schema declared.

No examples provided.

Install

How do I install the Paw Multiverse pet food recalls MCP server?

Paw Multiverse pet food recalls is a hosted endpoint at https://pawmultiverse.com/mcp-recalls, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pawmultiverse.com

# add to Claude Code
claude mcp add --transport http com-pawmultiverse-recalls 'https://pawmultiverse.com/mcp-recalls'
Common questions

What is the Paw Multiverse pet food recalls MCP server?

Paw Multiverse pet food recalls is an MCP server listed in the public MCP registry as com.pawmultiverse/recalls. Pet food recalls from US, UK, Canadian and French registers, kept after removal. This page covers its hosted endpoint (https://pawmultiverse.com/mcp-recalls).

Is the Paw Multiverse pet food recalls MCP server safe to use?

Paw Multiverse pet food recalls scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Paw Multiverse pet food recalls MCP server expose?

Paw Multiverse pet food recalls exposes 6 tools: check_pet_food_bag, get_recall_record, list_recall_registers, ask_recall_record, search_recalls, cross_border_recalls. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.

Does the Paw Multiverse pet food recalls MCP server require authentication?

No. We connected to Paw Multiverse pet food recalls without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Paw Multiverse pet food recalls MCP server still maintained?

Paw Multiverse pet food recalls is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Paw Multiverse pet food recalls MCP server?

VerifyMCP ran 12 checks on Paw Multiverse pet food recalls, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Paw Multiverse pet food recalls: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.