# Household Recall Watch (mcpb · household-recall-watch.mcpb)

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

- Trust score: 61/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `household-recall-watch.mcpb`: 61/100 (this document), [markdown](https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch.md), [page](https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpb`
- Transport: `stdio`
- SHA-256: `3e0073bc2fff21edfbac55edd549174ebfca8bd74e9617eac2d3446e95be3260`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 94 of 94 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1055 tokens (~131/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Household Recall Watch MCP server?

Household Recall Watch ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 3e0073bc2fff21edfbac55edd549174ebfca8bd74e9617eac2d3446e95be3260; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpb`
- SHA-256: `3e0073bc2fff21edfbac55edd549174ebfca8bd74e9617eac2d3446e95be3260`

### Verify on macOS / Linux

```bash
echo "3e0073bc2fff21edfbac55edd549174ebfca8bd74e9617eac2d3446e95be3260  household-recall-watch.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\household-recall-watch.mcpb).Hash -eq "3e0073bc2fff21edfbac55edd549174ebfca8bd74e9617eac2d3446e95be3260"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 61, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `search_product_recalls` (~155 tokens)

Search product recalls

Find recalls of household products (cribs, strollers, heaters, toys, appliances, e-bikes) and home medical devices by product name. Use when someone asks "has my <product> been recalled?". Searches US CPSC recalls and openFDA device recalls. Returns the hazard, the remedy, the date and a link.

Input parameters:

- `limit` (integer): How many results to return, newest first. Keep it small for voice: 3 to 5.
- `query` (string, required): Product name or type as the user said it, e.g. "crib mattress", "space heater".
- `since` (string): Only recalls on or after this date (YYYY-MM-DD). Default: one year ago.

Output parameters:

- `count` (integer)
- `disclaimer` (string)
- `notes` (array): Sources that answered live, but from a different URL than the plain request (for example an earlier CPSC start date, filtered here to the window).
- `query` (string)
- `results` (array)
- `since` (string)
- `spoken` (string): A short answer to read aloud.
- `warnings` (array): Sources that could not be reached, or were served only from a stale saved copy; the rest still answered.

### `search_food_recalls` (~137 tokens)

Search food recalls

Find US food recalls (undeclared allergens, contamination such as Listeria or Salmonella, foreign objects) by food or brand name. Use when someone asks whether a food they bought is recalled. Source: openFDA food enforcement reports.

Input parameters:

- `limit` (integer): How many results to return, newest first. Keep it small for voice: 3 to 5.
- `query` (string, required): Food, ingredient or brand, e.g. "peanut butter", "romaine", "ice cream".
- `since` (string): Only reports on or after this date (YYYY-MM-DD). Default: one year ago.

Output parameters:

- `count` (integer)
- `disclaimer` (string)
- `notes` (array): Sources that answered live, but from a different URL than the plain request (for example an earlier CPSC start date, filtered here to the window).
- `query` (string)
- `results` (array)
- `since` (string)
- `spoken` (string): A short answer to read aloud.
- `warnings` (array): Sources that could not be reached, or were served only from a stale saved copy; the rest still answered.

### `search_medicine_alerts` (~174 tokens)

Search medicine recalls and shortages

Find medicine recalls (US, openFDA drug enforcement) and medicine shortages (EU, European Medicines Agency) by brand or active ingredient. Use when someone asks whether their medicine is recalled or hard to get. Never advise stopping a medicine: the answer points to a pharmacist or doctor.

Input parameters:

- `limit` (integer): How many results to return, newest first. Keep it small for voice: 3 to 5.
- `query` (string, required): Medicine brand or active ingredient, e.g. "ibuprofen", "Ozempic", "insulin".
- `region` (string): "us" for FDA recalls only, "eu" for EMA shortages only, "all" for both.
- `since` (string): Only items on or after this date (YYYY-MM-DD). Default: one year ago.

Output parameters:

- `count` (integer)
- `disclaimer` (string)
- `notes` (array): Sources that answered live, but from a different URL than the plain request (for example an earlier CPSC start date, filtered here to the window).
- `query` (string)
- `results` (array)
- `since` (string)
- `spoken` (string): A short answer to read aloud.
- `warnings` (array): Sources that could not be reached, or were served only from a stale saved copy; the rest still answered.

### `search_eu_product_recalls` (~209 tokens)

Search EU product recalls

Find products flagged as dangerous in the European Union (toys, chargers, cosmetics, appliances, e-bikes, cars) by product, brand, model or barcode. Use when someone in Europe asks whether a product they bought was recalled or withdrawn. Source: EU Safety Gate weekly alerts (formerly RAPEX), up to the last 12 weekly reports. Returns the risk, the measure taken, the date and the official alert link.

Input parameters:

- `limit` (integer): How many results to return, newest first. Keep it small for voice: 3 to 5.
- `query` (string, required): Product, brand, model or barcode as the user said it, e.g. "usb charger", "Hyundai Ioniq 6", "4006381333931".
- `since` (string): Only alerts in weekly reports published on or after this date (YYYY-MM-DD). Default: 28 days ago. At most the 12 most recent weekly reports are read.

Output parameters:

- `attribution` (string): The source credit the European Commission requires on any reuse of Safety Gate alerts.
- `count` (integer)
- `disclaimer` (string)
- `notes` (array): Sources that answered live, but from a different URL than the plain request (for example an earlier CPSC start date, filtered here to the window).
- `query` (string)
- `results` (array)
- `since` (string)
- `spoken` (string): A short answer to read aloud.
- `warnings` (array): Sources that could not be reached, or were served only from a stale saved copy; the rest still answered.

### `watchlist_add` (~120 tokens)

Add to household watchlist

Remember a product, food or medicine the household owns, so check_my_household can watch it for recalls. Use when someone says "keep an eye on my <thing>". Pick the kind if it is clear; otherwise use "any".

Input parameters:

- `kind` (string): "product" for household goods and devices, "food", "medicine", or "any" to check every source.
- `name` (string, required): What to watch, as a short product/food/medicine name, e.g. "Graco stroller", "Tylenol".

Output parameters:

- `added` (boolean)
- `items` (array)
- `spoken` (string)

### `watchlist_list` (~29 tokens)

List household watchlist

Say what is on the household watchlist. Use when someone asks "what am I watching?".

Output parameters:

- `items` (array)
- `spoken` (string)

### `watchlist_remove` (~56 tokens)

Remove from household watchlist

Stop watching an item. Use when someone says "stop watching <thing>". Matches the name (case-insensitive) or the item id.

Input parameters:

- `name` (string, required): The item name as on the watchlist, or its id.

Output parameters:

- `items` (array)
- `removed` (boolean)
- `spoken` (string)

### `check_my_household` (~101 tokens)

Check my household for recalls

Check every item on the household watchlist against recent recalls and medicine shortages from all sources (CPSC, openFDA food/drug/device, EMA). Use when someone asks "has anything in my house been recalled?". Default window: the last 180 days.

Input parameters:

- `limit` (integer): Maximum matches to return, newest first.
- `since` (string): Only recalls on or after this date (YYYY-MM-DD). Default: 180 days ago.

Output parameters:

- `count` (integer)
- `disclaimer` (string)
- `matches` (array)
- `notes` (array): Sources that answered live, but from a different URL than the plain request (for example an earlier CPSC start date, filtered here to the window).
- `since` (string)
- `spoken` (string)
- `warnings` (array)
- `watched` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 61
- 2026-10-30: 60
- 2026-10-29: 60
- 2026-10-28: 59
- 2026-10-27: 59
- 2026-10-26: 58
- 2026-10-25: 58
- 2026-10-24: 57
- 2026-10-23: 57
- 2026-10-22: 56
- 2026-10-21: 56
- 2026-10-20: 55
- 2026-10-19: 55
- 2026-10-18: 54
- 2026-10-17: 54
- 2026-10-16: 54
- 2026-10-15: 53
- 2026-10-14: 53
- 2026-10-13: 52
- 2026-10-12: 48
- 2026-10-10: 48
- 2026-10-07: 48
- 2026-10-05: 48
- 2026-10-04: 48
- 2026-10-03: 48

## Common questions

### What is the Household Recall Watch MCP server?

Household Recall Watch is an MCP server listed in the public MCP registry as io.github.MGrin/household-recall-watch. Household recall checks over public CPSC, openFDA, EMA and EU Safety Gate data. No API key. This page covers its MCPB bundle (https://github.com/MGrin/recall-radar-mcp/releases/download/v0.2.1/household-recall-watch.mcpb).

### Is the Household Recall Watch MCP server safe to use?

Household Recall Watch scores 61 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Household Recall Watch MCP server expose?

Household Recall Watch exposes 8 tools: search_product_recalls, search_food_recalls, search_medicine_alerts, search_eu_product_recalls, watchlist_add, and 3 more. Their descriptions and schemas cost roughly 981 tokens of context every time the server is loaded.

### What licence is the Household Recall Watch MCP server under?

Household Recall Watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Household Recall Watch MCP server?

VerifyMCP ran 15 checks on Household Recall Watch, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Household Recall Watch: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/MGrin/recall-radar-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch.xml
- Changelog JSON feed: https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch.json
- HTML version of this page: https://verifymcp.io/servers/mgrin-household-recall-watch/household-recall-watch