Data Collection
recallradar.dev
Search and retrieve consumer product safety recall notices from multiple government sources by text, authority, jurisdiction, category, hazard, manufacturer, and date range, with detailed provenance information.
ENDPOINT 1
https://api.recallradar.dev/mcp
MCP server metadata
- Name
- recalls
- Version
- 1.0.0
Known tools 3
recalls_searchSearch consumer-product safety notices (CPSC US, EU Safety Gate, Health Canada, GOV.UK OPSS, ACCC AU, France RappelConso) by free text and/or authority, jurisdiction, category, hazard, manufacturer, strict-recall classification, and publication date range.
Inferred read-onlyrecalls_getFetch a full recall notice by integer id: affected products, parties (with roles), hazard + remedy text, and a `_provenance` subtree on every field (source, source_url, confidence).
Inferred read-onlyrecalls_sourcesThe source registry: each authority, its licence, redistributable flag, and homepage.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.recalls]
url = "https://api.recallradar.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"recalls": {
"type": "http",
"url": "https://api.recallradar.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: recalls
Remote MCP URL: https://api.recallradar.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"recalls": {
"url": "https://api.recallradar.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"recalls": {
"type": "http",
"url": "https://api.recallradar.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "recalls",
"transport": "streamable-http",
"url": "https://api.recallradar.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for recallradar.dev was fetched 2026-08-13T21:42:24.671Z.
recallradar.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.