mcpbeat Sign in

Recall Risk MCP Server

answering

Recall Risk is answering right now. Last checked 10 min ago. It exposes 1 tools.

Check a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand.

Uptime history 91 days of history · worst day 91%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
96 ms
Response time
average over 24h
open, no key
Access
streamable-http

Recall Risk missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add recall-risk --transport http https://cassandra.dropwatchhq.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://cassandra.dropwatchhq.com/mcp
~/.codex/config.toml
[mcp_servers.recall-risk]
url = "https://cassandra.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "recall-risk": {
      "url": "https://cassandra.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "recall-risk": {
      "type": "http",
      "url": "https://cassandra.dropwatchhq.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recall
recall_risk
Get the current complaint-velocity recall-risk signal for a tracked product/brand/model. Returns a 0-100 risk score, band, complaint velocity & acceleration, and severe-hazard share. This is a RISK SIGNAL from public complaint data, NOT an official recall or a claim the product is defective.

Endpoints

URLTransportStateLatencyChecked
https://cassandra.dropwatchhq.com/mcp streamable-http answering 84 ms 10 min ago

Alternatives to Recall Risk

same job, measured the same way
Recalert
by recalert

Search U.S. product recalls (CPSC, FDA, NHTSA, FSIS) by product, brand, model, or UPC code.

6 tools answering
Recall Canary
by recallcanary

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

2 tools answering
PlainRecords: U.S. recalls in plain English
by plainrecords

U.S. FDA, CPSC and NHTSA recalls by product, brand, lot code or car, plus owner complaints. Daily.

7 tools answering
RecallScout
by yc-droid

US vehicle, car-seat, product and food recalls, VIN decoding and crash ratings (NHTSA, CPSC, FDA).

8 tools answering
Recall Check
by openkrill

Check US recalls for a car, a baby product, a food or a medicine in the official recall databases.

7 tools answering
FDA Recall Checker (openFDA)
by wyeming95-rgb

Check products against FDA food, drug and device recalls; drug labels, NDC, 510(k) via openFDA

answering
Zovo Product Recall Check
by theluckystrike

Inventory recall screening

3 tools answering
Cpsc
by pipeworx-io

CPSC MCP — US consumer-product safety recalls (CPSC, free, no auth).

433 installs/wk 46 tools answering

Recall Risk — questions

Answers built from our own checks of this server.

What can Recall Risk do?
It exposes 1 tools, read directly from the server on our last check. Among them: recall_risk. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Recall Risk working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.
How do I connect Recall Risk?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Recall Risk need an API key?
No. Recall Risk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Recall Risk?
It answers our handshake in 96 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.