Zovo Product Recall Check
REMOTE · PRODUCT-RECALLS.ZOVO.ONE
Inventory recall screening
Available components
Last scanned (6 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 24 Oct 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://product-recalls.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7424e2cfcc5c09861338a6f4d93812a9 |
| SANs: zovo.one, product-recalls.zovo.one, *.product-recalls.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of product-recalls.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://product-recalls.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://product-recalls.zovo.one/mcp | HTTPS enforced | 301 | https://product-recalls.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_inventory_for_recalls Check inventory for recalls ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| coverage | string | yes | – |
| downloads | object | yes | – |
| failed_years | array | yes | – |
| kind | string | yes | – |
| recalled_since_year | number | yes | – |
| records_checked | number | yes | – |
| retrieved_utc | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| total_items | number | yes | – |
No examples provided.
get_recall_details Get recall details ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recall_number | array | yes | One to ten recall numbers. Example: ["27024"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| failed_years | array | yes | – |
| kind | string | yes | – |
| retrieved_utc | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| total_count | number | yes | – |
No examples provided.
search_recalls Search recalls ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| date_from | string | yes | – |
| date_to | string | yes | – |
| downloads | object | yes | – |
| exported_count | number | yes | – |
| failed_years | array | yes | – |
| keywords | string | yes | – |
| kind | string | yes | – |
| match_in | string | yes | – |
| retrieved_utc | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| total_count | number | yes | – |
No examples provided.
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.
remote · product-recalls.zovo.one
claude mcp add --transport http theluckystrike-product-recalls 'https://product-recalls.zovo.one/mcp'
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.