World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key.
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 0/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 7/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 7/100 |
품질: 기본 점검 3/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있지만 먼저 준비가 필요해요
키 필요 없음, 설치 필요 없음 · 컴퓨터용 Claude 앱(Windows 또는 Mac)에서만 되고 웹이나 모바일은 안 돼요
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에 연결되는 앱 쓰기
B · 기타에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 Household Recall Watch에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Household Recall Watch에 연결되는 앱 쓰기
Cursor는 아직 Household Recall Watch에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Household Recall Watch에 연결되는 앱 쓰기
VS Code는 아직 Household Recall Watch에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Household Recall Watch에 연결되는 앱 쓰기
이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 19일 점검
레지스트리 이름이 GitHub 계정 MGrin 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 2개월 전
MIT 사용
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/mgrin-household-recall-watch)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 2개월 전 변경됐고, 최신 버전(0.2.1)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 이 항목 Household Recall Watch | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| 기본 점검 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 라이선스 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
A self-hosted Model Context Protocol server that lets a voice assistant answer household safety questions from public government recall data:
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
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
| env | default | meaning |
|---|---|---|
PORT | 3000 | HTTP port |
HOST | 127.0.0.1 (0.0.0.0 in Docker) | bind address |
WATCHLIST_PATH | ./data/watchlist.json | where 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_PROVIDER | openai if OPENAI_API_KEY is set, else scripted | openai, ollama or scripted |
OPENAI_API_KEY | *(none)* | OpenAI key; never logged or sent to the browser |
OPENAI_MODEL | gpt-6-luna | any Chat Completions model with function calling |
OPENAI_REASONING_EFFORT | none | sent 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_URL | https://api.openai.com/v1 | for an OpenAI-compatible gateway |
OLLAMA_URL / OLLAMA_MODEL | http://127.0.0.1:11434 / llama3.1 | Ollama's OpenAI-compatible endpoint (/v1/chat/completions) |
MCP_URL | this process's own /mcp | point 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 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.
| adapter | status |
|---|---|
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). |
ollama | The 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.
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.
| tool | what it answers | sources |
|---|---|---|
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.
| source | endpoint | terms |
|---|---|---|
| US Consumer Product Safety Commission | saferproducts.gov/RestWebServices/Recall | US government work, public domain |
| openFDA enforcement reports (food, drug, device) | api.fda.gov/{food,drug,device}/enforcement.json | public 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 catalogue | ema.europa.eu/en/documents/report/shortages-output-json-report_en.json | reuse permitted with EMA acknowledged as the source (legal notice); every EMA item carries its EMA URL |
| European Co