Recall Canary MCP server
com.recallcanary/recall-canaryrecallcanary.comstreamable-httpv1.7.0Scanned
U.S. federal product recalls and safety notices from FDA, FSIS, CPSC, and NHTSA, in one schema.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.
What the Recall Canary MCP server can do
The Recall Canary MCP server is published by recallcanary.com, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.7.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
get_recallFetch the full Recall Canary record for a single U.S.No findings
Why it is in this group
- The name "get_recall" says "get": a word for reading.
Description, as the server wrote it Fetch the full Recall Canary record for a single U.S. federal recall, FSIS public health alert or CPSC safety warning (`record_kind`), 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 Recall Canary page URL to link when citing it (`url`), the agency's own notice (`source_url`), 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`). Pass `detail: "brief"` unless you need related records or the timeline. Read-only.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_recallsSearch the Recall Canary index of U.S.No findings
Why it is in this group
- The name "search_recalls" says "search": a word for reading.
Description, as the server wrote it 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. Results also hold FSIS public health alerts and CPSC safety warnings, which are not recalls (`record_kind`). Returns up to 50 matching records per page (fewer with `limit`) with abbreviated content (title, firm, severity, date, the Recall Canary page URL to link when citing it, and the agency notice URL); call get_recall to fetch the full record. With a keyword, the best matches come first, open records before ended ones on each page, 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:24 UTC, unchanged since Oct 28, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://recallcanary.com/.well-known/oauth-protected-resource
- Authorization servers
- https://recallcanary.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:get_recallOnly readsdescriptioninputSchema
- Changed:search_recallsOnly readsdescriptioninputSchema
Tools2 changed.~2 changedView diff
- Changed:get_recallOnly readsdescriptioninputSchema
- Changed:search_recallsOnly readsdescriptioninputSchema
Tools2 changed.~2 changedView diff
- Changed:get_recallOnly readsdescription
- Changed:search_recallsOnly readsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:search_recallsOnly readsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:search_recallsOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:search_recallsOnly readsinputSchema
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http recall-canary https://recallcanary.com/data/mcpclaude mcp add --transport http recall-canary https://recallcanary.com/data/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__recall-canary__search_recalls",
"mcp__recall-canary__get_recall"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as recall-canary. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.recallcanary/recall-canary/verify?hash=d69b4468e82743a179c9563c538e4e8cdcffe4e559a9ab6eb846a28477d9e371" | jq -e '.changed == false'Pinned hash d69b4468e827, from Nov 19, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.recallcanary/recall-canary/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.recallcanary/recall-canary)Source: MCP Registry. Synced Nov 19, 2026, 10:17 UTC.
Recall Canary MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Recall Canary MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Recall Canary MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Recall Canary MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Recall Canary MCP server have?
- 2 tools: 2 read. search_recalls and get_recall.
Does the Recall Canary MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Recall Canary MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Recall Canary MCP server changed its tools?
- Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.