RecallRadar

io.github.vanja-ivancevicPublished by GitHub account vanja-ivancevicv1.0.0Updated Nov 14, 2026

Historical consumer-product recalls and safety notices from official sources.

The publisher's own server: Recall

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Searches and retrieves official consumer-product recall and safety notices from six government authorities, with per-field provenance and source links.

What you can do
  • Search recall notices by free text, authority, jurisdiction, category, hazard, manufacturer, strict-recall flag and publication date range, returning up to 100 results.
  • Fetch a full notice by id: affected products, parties and their roles, hazard and remedy text.
  • Inspect the source registry, including each authority's licence, redistributable flag and homepage.
  • Trace every field back to its source, source URL and confidence via provenance data.
When to use it
Useful when checking whether a product, brand or manufacturer has been recalled, or when compiling safety research across US, EU, Canadian, UK, Australian and French authorities with citable sources.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared, and no authentication is declared.
Before you install
Read-only lookup tools, but results are third-party official data: cite the provided source URL verbatim rather than inventing one, and check each authority's licence and redistributable flag before republishing notices.

Installation

In SourceWeft

  1. Open RecallRadar 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/io.github.vanja-ivancevic%2Frecallradar/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": {
    "recallradar": {
      "type": "http",
      "url": "https://api.recallradar.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

recalls_get

Get a safety notice

Fetch 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). Cite source_url verbatim — do not fabricate.

Parametersidrequired

recalls_sources

List sources

The source registry: each authority, its licence, redistributable flag, and homepage.

Takes no parameters.

Version history

1
  1. v1.0.0LatestNov 13, 2026

Score

75% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Recall integrations