Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
mcpb https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpbClaude Code has no install link for a local command. Copy the command below and run it in a terminal.
claude mcp add io.github.mgrin-household-recall-watch -- mcpb https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpbRun in a terminal.
{ "mcpServers": { "io.github.mgrin-household-recall-watch": { "command": "mcpb", "args": [ "https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpb" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A self-hosted Model Context Protocol server that lets a voice assistant answer household safety questions from public government recall data:
Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key.
Every answer carries a short spoken sentence for the voice reply, plus structured detail with the
source URL and date of every item. No API keys, no accounts, no LLM needed to run it.
Built for the Amazon Developer Hackathon, Alexa+ track. MCP spec 2025-11-25, Streamable HTTP,
stateless, @modelcontextprotocol/sdk 1.30.1.
This is a simulated smart-display experience backed by a real MCP server; it has not been connected to an Alexa+ device. See the judge-run guide, the verification record and the friction log.
Not medical or safety advice. Recall and shortage data can be incomplete or late. Always check the linked notice, and ask a pharmacist, doctor or the manufacturer before acting. Never stop a prescribed medicine on your own.
Node 20 or newer. One process serves the MCP server at /mcp, the voice UI at / and the agent at
POST /api/ask:
npm ci && npm start
# recall-radar MCP server: http://127.0.0.1:3000/mcp (health: /healthz, ...)
# Recall Radar voice UI: http://127.0.0.1:3000/ (agent: POST /api/ask, model: Scripted mode, no LLM)
Judge path.
npm start, open http://127.0.0.1:3000/. The badge reads Scripted mode,
no LLM: a fixed phrase-to-tool mapping stands in for the model, but the MCP calls and the recall data
are real and live. Try the suggestion chips, or drive it from the URL:
http://127.0.0.1:3000/?q=Watch%20my%20crib%20mattress&q=Has%20anything%20in%20my%20house%20been%20recalled%3FOPENAI_API_KEY outside the repository and run npm start. The badge
identifies the selected model (gpt-6-luna by default). This path was run live on 2026-10-02
with that model; other models were not exercised (EVIDENCE.md).Or Docker:
docker build -t recall-radar-mcp . && docker run --rm -p 3000:3000 recall-radar-mcp
docker run --rm -p 3000:3000 -e OPENAI_API_KEY recall-radar-mcp # with a model
Endpoints: POST /mcp (MCP Streamable HTTP, stateless: no session id, no GET stream), GET /healthz,
GET / (the UI), POST /api/ask ({"q": "...", "history": [...]}), GET /api/config, GET /api/watchlist.
A stdio entry is also included: npm run start:stdio.
The stdio entry is listed in the MCP Registry as
io.github.MGrin/household-recall-watch (server.json). Its package is an MCPB bundle
attached to the GitHub release; npm run pack:mcpb rebuilds it and prints the SHA-256 that
server.json must carry. The bundle keeps its watchlist at ~/.recall-radar/watchlist.json.
Publishing is .github/workflows/publish-mcp.yml: on a v* tag (or gh workflow run publish-mcp.yml --ref vX.Y.Z) it checks the release bundle against server.json, then publishes with GitHub OIDC.
Attach the bundle to the GitHub release before the workflow runs.
If your machine reaches the internet only through an HTTP proxy, Node's built-in fetch ignores
HTTPS_PROXY unless you set NODE_USE_ENV_PROXY=1 (Node 24+). That applies to the OpenAI calls too.
The track allows "a simulated Alexa+ experience in a web app"; this is ours, named Recall Radar and using no third-party marks.
SpeechRecognition). Where that is missing the mic is disabled and the text box does the same job.
Microphone behavior still needs a real-device check.speechSynthesis, with a mute toggle; a light bar along the bottom edge shows
listening, thinking and speaking. Speaker output still needs a real-device check.?q=... asks on load; repeat it (?q=a&q=b) for a scripted walkthrough, and add mute=1 for silent
capture.src/agent/)agent.ts is a real MCP client (SDK Client + StreamableHTTPClientTransport): per question it
connects to /mcp, lists the tools, maps them to the model's function format and runs the tool-call
loop, capped at 6 model steps. Tool results go back to the model as the tool's structuredContent.
A ModelAdapter (types.ts) is one method: messages + tools in, text or tool calls out.
The system prompt (prompt.ts) keeps answers voice-first (two or three sentences: hazard, official
remedy, what to do now), grounds every claim in a tool result, and forbids medical advice beyond the
official remedy text.
MCP Inspector (no LLM key needed):
npx @modelcontextprotocol/inspector
In the Inspector UI choose transport Streamable HTTP, URL http://127.0.0.1:3000/mcp, Connect,
then Tools → List Tools and call any tool.
From the terminal, with the bundled SDK client:
npm run call # list tools
npm run call -- search_product_recalls '{"query":"stroller","limit":3}'
npm run call -- watchlist_add '{"name":"crib mattress","kind":"product"}'
npm run call -- check_my_household '{}'
Eight tools. search_eu_product_recalls was added in v0.2.0, after the demo video was recorded; the
video shows and says seven.
Each tool declares a zod input schema and an outputSchema; results come back as structuredContent
(validated by the SDK) and as text. Each recall is normalised to:
{ source, id, title, hazard, remedy, date /* YYYY-MM-DD */, products[], url, summary /* one spoken sentence */ }
If one upstream is down, the others still answer and the result lists a warning; if every source for
a question is down, the tool returns a clean MCP tool error (isError: true).
CPSC's API has answered some URLs and 503'd others, consistently per URL, for days at a time (seen
2026-10-02 to 10-04). So a CPSC read tries the window's own URL, then the same window without the
product filter, then up to three EARLIER start dates (the 1st of the month, the 1st of the month
before, a few dates that answered during the outage), and filters the rows here to the requested
window: at most 6 requests in 20 seconds. When an earlier URL served the answer, the result says so
in notes, naming that URL. Every good CPSC response is also saved beside the watchlist
(cpsc-cache.json, the last 8 URLs, each with its fetch time). If every live attempt fails, the
rows of the freshest saved copy that fall inside the window are served, each summary ending
"From a saved copy of CPSC data fetched ; CPSC could not be reached live", and a warning
names the fetch time; with no saved copy, CPSC is reported unavailable. Nothing else is invented.
Every upstream request
has a 10-second timeout (20 seconds for Safety Gate). The EMA file is cached for an hour in memory,
because EMA rate-limits repeated downloads. Safety Gate publishes one weekly report every Friday, each
about 200-300 KB and 3-6 seconds to serve (2026-10-02): a search reads at most 12 reports, four at a
time, caches the index for an hour and each published report for the life of the process. A cold
four-week search took about 5 seconds; a repeat answers from the cache. When the window holds more
than 12 reports, since in the answer is the oldest report actually read.
openFDA has no per-recall web page, so an FDA item's url is the openFDA API query that returns exactly
that recall (search=recall_number:"…").
The Safety Gate attribution, verbatim: "Alerts from the Rapid Alert System for dangerous non-food products, published free of charge on the Safety Gate website (https://ec.europa.eu/safety-gate-alerts) © European Union, 2005 – 2026". The Commission also notes that brands in the alerts may have been used by the economic operators without the owner's permission.
src/sources/ema.ts adapts our own earlier code from the ema-medicines-watch Apify Actor (same
author): the EMA dd/mm/yyyy date parser, the {meta, data[]} shape check and the truncated-file guard.
src/sources/safetygate.ts adapts the eu-recall-watchlist Apify Actor (same author): the Safety Gate
XML parser settings, CDATA handling, the run-together measures field and the verbatim attribution.
Everything else was written for this entry.
npm run build # tsc -> dist/
npm test # vitest, against recorded fixtures in test/fixtures (no network)
LIVE=1 npm test # also runs test/live.test.ts against the real APIs
test/agent.test.ts runs the agent loop with the scripted adapter against the real MCP server over HTTP
(upstreams mocked to fixtures), plus the /api/* routes and the static UI. test/openai.test.ts runs the
OpenAI adapter against a mocked Chat Completions endpoint, alone and inside a multi-step agent loop.
The end-to-end test starts the HTTP server, connects with the SDK Client over
StreamableHTTPClientTransport, checks that protocol 2025-11-25 is negotiated, lists the tools and
calls every one, with upstream fetch routed to fixtures.
MIT, © 2026 Nikita Grishin Limited. See LICENSE. Friction log: FRICTION.md.
© 2026 MCP Directory.
Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key.
{ "mcpServers": { "io.github.mgrin-household-recall-watch": { "command": "mcpb", "args": [ "https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpb" ] } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Household Recall Watch runs locally over stdio.
Last checked 2026-11-09. Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key.