mcpbeat

Recall Risk MCP Server

com.dropwatchhq/recall-risk
answering

Recall Risk is answering right now. Last checked 6 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 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
68 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add recall-risk --transport http https://cassandra.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "recall-risk": {
      "url": "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
{
  "mcpServers": {
    "recall-risk": {
      "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 57 ms 6 min ago

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 68 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 with the file path 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 68 ms on average, which is faster than 94% 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.