Recall Canary

com.recallcanaryPublished by recallcanary.comOfficial publisherv1.5.0Updated Nov 7, 2026

U.S. federal product recalls from FDA, FSIS, CPSC, and NHTSA, in one schema.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Searches U.S. federal product recalls from FDA, FSIS, CPSC and NHTSA in one schema and returns full recall records.

What you can do
  • Search recalls by keyword, agency, severity, category, distribution state, hazard, firm, lifecycle or date window, up to 50 per page
  • Fetch a single recall's full record by agency and slug, including hazard, affected products with lot codes and UPCs, consumer action, distribution and source link
  • Distinguish preliminary press-release records from canonical records and follow linked recalls
When to use it
Useful when checking whether a product, brand or firm has been recalled, or when summarizing recall activity by agency, hazard or date range for consumers, support or compliance work.
Requirements
Remote MCP endpoint at recallcanary.com over streamable HTTP; no authentication, environment variables or headers are declared.
Before you install
Some fields are written by a language model from agency text; the agency source page is authoritative and should be cited. Preliminary records carry no severity or product list. A missing match does not prove a product is safe.

Installation

In SourceWeft

  1. Open Recall Canary in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.recallcanary%2Frecall-canary/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "recall-canary": {
      "type": "http",
      "url": "https://recallcanary.com/data/mcp"
    }
  }
}

Tools

2

search_recalls

Search U.S. federal product recalls

Search the Recall Canary index of U.S. federal product recalls (FDA, FSIS, CPSC, NHTSA) by keyword, agency, severity, category, distribution state, hazard, firm, lifecycle (open or ended), or date window. Returns up to 50 matching records per page with abbreviated content (title, firm, severity, date, and the canonical URL of each); call get_recall to fetch the full record. With a keyword, the best matches come first unless `sort` says otherwise. Unknown agency, severity, category, state, status and date values are rejected with an error message describing the allowed values. An unknown `hazard` or `firm` is also an error. Read-only.

Parametersqtodatefirmfrompagesortstateagencyhazardstatuscategory+1 more

get_recall

Get one recall by agency and slug

Fetch the full Recall Canary record for a single U.S. federal recall, given the agency and slug returned by search_recalls. Includes the hazard description, the affected product list with lot codes and UPCs, the recommended consumer action, distribution, the agency source link, and the firm slug (`firm.slug`, with `firm.page_url` when the firm has a page) for search_recalls' `firm` filter. Also resolves preliminary agency press releases: an orphan, or a linked one that kept its own URL (its recalls in `linked_recalls`). Read-only.

Parametersslugrequiredagencyrequired

Version history

3
  1. v1.5.0LatestNov 7, 2026
  2. v1.4.0Oct 30, 2026
  3. v1.3.0Oct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.