MCP server
Model Context Protocol server
Connect AI agents (Claude, Cursor, OpenAI Assistants, any MCP client) to RecallRadar via the Model Context Protocol. Every recalled product returned carries its source_record_url inline.
https://recallradar-api.vercel.app/mcp — requires a paid API key.Quick-start (Claude Desktop)
Add the server to your claude_desktop_config.json:
Or connect directly to the remote MCP endpoint: https://recallradar-api.vercel.app/mcp
Tools
recalls_searchSearch recall notices by free text, authority, jurisdiction, category, hazard type, or manufacturer. Returns paginated results with title, summary, risk level, and source URL.
Parameters
qauthorityjurisdictioncategory_codehazardmanufacturerpublished_frompublished_tolimitcursorrecalls_getFetch a single recall notice by its ID. Returns the full document including all provenance fields, products, parties, and the canonical source_record_url.
Parameters
idrecalls_sourcesList all ingested source authorities with their license, homepage, and last-ingested timestamp.
recalls_coverageReturn per-authority and per-category counts, date ranges, and field-fill statistics. Requires a paid API key.
Parameters
authoritycategory_codeExample tool call
JSON-RPC 2.0 payload sent to the MCP server:
Citation: When an AI agent surfaces a recall to end-users, always include the source_record_url as the authoritative link back to the original regulator page. This satisfies the redistribution attribution requirement for all five source licences.