# Zovo Product Recall Check (remote · product-recalls.zovo.one)

Inventory recall screening

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `product-recalls.zovo.one`: 76/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls.md), [page](https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls)

## Channel facts

- Endpoint: `https://product-recalls.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 511 tokens (~127/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Product Recall Check MCP server?

Zovo Product Recall Check is a hosted endpoint at https://product-recalls.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-product-recalls 'https://product-recalls.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-product-recalls": {
      "url": "https://product-recalls.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-product-recalls": {
      "type": "http",
      "url": "https://product-recalls.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-product-recalls]
url = "https://product-recalls.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-product-recalls": {
      "type": "remote",
      "url": "https://product-recalls.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-product-recalls --url 'https://product-recalls.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-product-recalls:
    url: "https://product-recalls.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-product-recalls": {
      "Transport": "http",
      "Url": "https://product-recalls.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-product-recalls -t streamable-http -u 'https://product-recalls.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-product-recalls": {
      "type": "http",
      "url": "https://product-recalls.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-24 (score 76, +1)

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

### 2026-10-23 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 75)

First indexed and scored.

## MCP tools (3)

### `check_inventory_for_recalls` (~158 tokens)

Check inventory for recalls

Use this when the user wants to check my inventory for recalls, check items against cpsc recalls, or run a resale recall check. Reads live consumer-product recall data and generates XLSX and CSV screening files for 1–100 items, from a chosen year since 2000. Word matches require verification; models written with spaces can be missed. Do not use for food, drugs or vehicle recalls.

Input parameters:

- `items` (array, required): Stock list in input order, 1–100 items. Example: [{"product":"thermal laminator","model":"TL1302Z"}].
- `recalled_since_year` (integer): First announcement year through the current UTC year; defaults to current year minus 14. Example: 2026.

Output parameters:

- `counts` (object)
- `coverage` (string)
- `downloads` (object)
- `failed_years` (array)
- `kind` (string)
- `recalled_since_year` (number)
- `records_checked` (number)
- `retrieved_utc` (string)
- `rows` (array)
- `source` (string)
- `source_url` (string)
- `total_items` (number)

### `search_recalls` (~195 tokens)

Search recalls

Use this when the user wants product recalls, a recall list, or a consumer product recall search. Searches live consumer-product data by keyword and dates touching at most 15 calendar years since 2000; previews up to 20 rows and exports the newest 2,000 to XLSX and CSV. Do not use for food, drugs or vehicle recalls.

Input parameters:

- `date_from` (string): Inclusive YYYY-MM-DD from 2000, defaults to 365 days before date_to. Example: 2026-10-01.
- `date_to` (string): Inclusive YYYY-MM-DD no later than today UTC; defaults to today UTC. Example: 2026-10-21.
- `keywords` (string): Product, brand, hazard, UPC or model keywords; blank lists the date range. Example: laminator.
- `match_in` (string): Field for word matching; default any. Example: hazard.

Output parameters:

- `coverage` (string)
- `date_from` (string)
- `date_to` (string)
- `downloads` (object)
- `exported_count` (number)
- `failed_years` (array)
- `keywords` (string)
- `kind` (string)
- `match_in` (string)
- `retrieved_utc` (string)
- `rows` (array)
- `source` (string)
- `source_url` (string)
- `total_count` (number)

### `get_recall_details` (~101 tokens)

Get recall details

Use this when the user wants cpsc recalls, a recalled products list, or is this product recalled and has a recall number. Reads full live records for 1–10 recall numbers, including hazard, remedy, contact, retailers, units, UPCs and image links; missing records receive per-number errors. Do not use for recalls outside consumer products.

Input parameters:

- `recall_number` (array, required): One to ten recall numbers. Example: ["27024"].

Output parameters:

- `coverage` (string)
- `failed_years` (array)
- `kind` (string)
- `retrieved_utc` (string)
- `rows` (array)
- `source` (string)
- `source_url` (string)
- `total_count` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls#diagnostics

## Score history

- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75

## Common questions

### What is the Zovo Product Recall Check MCP server?

Zovo Product Recall Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/product-recalls. Inventory recall screening. This page covers its hosted endpoint (https://product-recalls.zovo.one/mcp).

### Is the Zovo Product Recall Check MCP server safe to use?

Zovo Product Recall Check scores 76 out of 100 on VerifyMCP. 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 Zovo Product Recall Check MCP server expose?

Zovo Product Recall Check exposes 3 tools: check_inventory_for_recalls, search_recalls, get_recall_details. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.

### Does the Zovo Product Recall Check MCP server require authentication?

No. We connected to Zovo Product Recall Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Product Recall Check MCP server still maintained?

Zovo Product Recall Check is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://product-recalls.zovo.one/mcp
- Website: https://product-recalls.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-product-recalls/product-recalls