Recalert MCP server

• Registry nameus.recalert/mcpverified in the MCP registry

The registry name sits under recalert.us. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools6
• Server calls itselfrecalert-mcp
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 192 ms.

• Its tools do every use case we checked: search federal recalls for a single product; check a product catalog against recalls nightly.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer301 ms
• Space in an agent's context≈ 641 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 78 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 2 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_recalls

  Free. Search U.S. product recalls from CPSC, FDA, NHTSA and FSIS by keyword, brand, model or source. Sorted by the real recall date. No api_key required. This is the free hook - use get_recall_detail or check_upcs for the unified/paid data.

• list_agencies

  Free. Lists the four U.S. federal agencies Recalert covers, with how many recalls are indexed from each and the date of the most recent one. No api_key required.

• check_upcs

  Paid - the main action. Cross-checks up to 500 UPCs against Recalert's unified recall database in one call. Requires api_key (get one free at https://recalert.us/en/data). Costs 10 credits per UPC checked ($0.01/UPC).

• get_recall_detail

  Paid. Returns the full unified-schema record for one specific recall (fuente + numero_oficial): hazard, remedy, manufacturer, distributor, official URL, resolved recall date and versioned metadata. Requires api_key. Costs 2 credits…

• get_data_notes

  Free. Known data-quality caveats so you can cite this dataset correctly: which date field is authoritative per agency, known ingestion gaps, and coverage per source. Read this before computing statistics from Recalert data. No api_key…

• get_pricing

  Free. Returns Recalert's pricing: human subscription tiers and the agent/API credit packages and per-call costs for this MCP server. No api_key required.