原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Household Recall Watch

作者:MGrin版本 0.2.1i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.MGrin/household-recall-watch

安装方法

What it does

Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分7/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 Household Recall Watch 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Household Recall Watch,或回答中出现 Household Recall Watch 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Household Recall Watch

Household Recall Watch 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Household Recall Watch 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Household Recall Watch

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Household Recall Watch 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 Household Recall Watch

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Household Recall Watch 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 Household Recall Watch

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Household Recall Watch 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Household Recall Watch 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.2.1
分类i
其他
发布到注册中心i
2026年10月4日
代码最后更新i
2026年10月4日
作者
MGrin
软件包
mcpb: …/household-recall-watch.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 MGrin 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于2个月前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/mgrin-household-recall-watch.svg)](https://mcp.popnx.com/en/servers/mgrin-household-recall-watch)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20693 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20693 个服务器的 50% 更新
  • 基础检查结果等于或优于此分类中其他 20693 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Household Recall Watch 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于2个月前,最新版本(0.2.1)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Household Recall Watch
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/44/44/41/44/4
许可证MITAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Recall Radar — an MCP server and voice front end for "has anything in my house been recalled?"

A self-hosted Model Context Protocol server that lets a voice assistant answer household safety questions from public government recall data:

  • US product recalls (CPSC) and home medical-device recalls (FDA),
  • US food recalls (FDA),
  • US medicine recalls (FDA) and EU medicine shortages (European Medicines Agency),
  • EU dangerous-product alerts (EU Safety Gate, formerly RAPEX),
  • and a household watchlist the assistant checks proactively: *"has anything I own been recalled since the summer?"*

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.

Run it (one command)

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.

  1. No key, scripted mode. 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%3F
  2. With a model. Set OPENAI_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

envdefaultmeaning
PORT3000HTTP port
HOST127.0.0.1 (0.0.0.0 in Docker)bind address
WATCHLIST_PATH./data/watchlist.jsonwhere the household watchlist is stored; CPSC's last good responses are saved beside it as cpsc-cache.json
ALLOWED_ORIGINS*(none)*extra browser Origins allowed besides localhost (comma-separated, * for any)
MODEL_PROVIDERopenai if OPENAI_API_KEY is set, else scriptedopenai, ollama or scripted
OPENAI_API_KEY*(none)*OpenAI key; never logged or sent to the browser
OPENAI_MODELgpt-6-lunaany Chat Completions model with function calling
OPENAI_REASONING_EFFORTnonesent as reasoning_effort; GPT-6 models refuse function tools on Chat Completions without none. Set omit for a model that rejects the field
OPENAI_BASE_URLhttps://api.openai.com/v1for an OpenAI-compatible gateway
OLLAMA_URL / OLLAMA_MODELhttp://127.0.0.1:11434 / llama3.1Ollama's OpenAI-compatible endpoint (/v1/chat/completions)
MCP_URLthis process's own /mcppoint the agent at another Recall Radar MCP server

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 voice front end (a simulated smart display)

The track allows *"a simulated Alexa+ experience in a web app"*; this is ours, named Recall Radar and using no third-party marks.

  • Push to talk: hold the mic button (or the space bar) and speak; it uses the browser's Web Speech API (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.
  • Spoken reply through 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.
  • Tool trace: a chip for every MCP tool the agent called, with its argument and latency, so a viewer can see the answer came from the MCP server.
  • Recall cards: source, date, title, hazard, remedy, the watchlist item it matched, and a link to the official notice.
  • Household watchlist panel (add with the + box or by voice, remove with ×; both go through the agent), and a transcript.
  • ?q=... asks on load; repeat it (?q=a&q=b) for a scripted walkthrough, and add mute=1 for silent capture.
The agent (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.

adapterstatus
openai (openai.ts)OpenAI Chat Completions with tools over plain fetch, no SDK. Unit-tested against recorded-shape responses, including a 3-step tool loop. Run against the live API with gpt-6-luna on 2026-10-02 (EVIDENCE.md).
ollamaThe same class pointed at Ollama's OpenAI-compatible endpoint. Untested: Ollama was not installed on the build machine.
scripted (scripted.ts)Deterministic: a few phrasings map to one tool call, and the reply is the tool's own spoken sentence (first item only). Used by the tests and the no-key demo.

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.

Try it

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 '{}'

Tools

Eight tools. search_eu_product_recalls was added in v0.2.0, after the demo video was recorded; the video shows and says seven.

toolwhat it answerssources
search_product_recalls"Has my stroller / space heater / crib been recalled?"CPSC, openFDA device
search_food_recalls"Is there a recall on peanut butter?" "Any listeria recalls?"openFDA food
search_medicine_alerts"Is my insulin recalled or short?" (region: us, eu, all)openFDA drug, EMA shortages
watchlist_add"Keep an eye on my Graco stroller." (kind: product, food, medicine, any)local file
watchlist_list"What am I watching?"local file
watchlist_remove"Stop watching the stroller."local file
search_eu_product_recalls (v0.2.0)"Was my USB charger recalled in the EU?" By product, brand, model or barcode (default: last 28 days, at most the 12 latest weekly reports)EU Safety Gate
check_my_household"Has anything in my house been recalled?" (default: last 180 days)CPSC, openFDA, EMA, by item kind (not Safety Gate)

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.

Data sources and terms

sourceendpointterms
US Consumer Product Safety Commissionsaferproducts.gov/RestWebServices/RecallUS government work, public domain
openFDA enforcement reports (food, drug, device)api.fda.gov/{food,drug,device}/enforcement.jsonpublic domain / CC0 per open.fda.gov/license; openFDA's own disclaimer: do not rely on it for medical-care decisions. Keyless use is rate-limited (terms).
European Medicines Agency, medicine shortages catalogueema.europa.eu/en/documents/report/shortages-output-json-report_en.jsonreuse permitted with EMA acknowledged as the source (legal notice); every EMA item carries its EMA URL

| European Co

只显示了开头部分;其余内容请在仓库中阅读