io.github.cyanheads/cpsc-recalls-mcp-server
REMOTE · CPSC-RECALLS.CASEYJHAND.COM · 2 COMPONENTS
US consumer product recalls from the CPSC: hazards, remedies, and affected products.
Available components
Last scanned (8 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2165 tokens (~541/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 current MCP spec version (2026-07-28).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.
- 29 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cpsc_get_recent” rewrote its description, which is the text the model reads security
- Tool “cpsc_search_recalls” rewrote its description, which is the text the model reads security
- Tool “cpsc_get_recall” rewrote its description, which is the text the model reads security
- Schema quality: 471 → 541 ▼ functional
- Server version: 0.3.0 → 0.3.1 functional
- “cpsc_search_recalls” reworded the description of “title_search” cosmetic
- “cpsc_get_recall” reworded the description of “recall_number” cosmetic
- “cpsc_get_recent” reworded the description of “limit” cosmetic
- “cpsc_search_recalls” reworded the description of “description_search” cosmetic
- “cpsc_search_recalls” reworded the description of “distributor” cosmetic
- “cpsc_search_recalls” reworded the description of “hazard_search” cosmetic
- “cpsc_search_recalls” reworded the description of “importer” cosmetic
- “cpsc_search_recalls” reworded the description of “limit” cosmetic
- “cpsc_search_recalls” reworded the description of “manufacturer” cosmetic
- “cpsc_search_recalls” reworded the description of “product_name” cosmetic
- “cpsc_search_recalls” reworded the description of “remedy” cosmetic
- “cpsc_search_recalls” reworded the description of “retailer” cosmetic
- 28 Oct 26 +3
- Schema quality: 598 → 471 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- New resource “cpsc-recalls-guide” functional
- Server version: 0.2.3 → 0.3.0 functional
- 25 Oct 26 0
- Server version: 0.2.2 → 0.2.3 functional
- 9 Oct 26 0
- Server version: 0.2.1 → 0.2.2 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- Server version: 0.2.0 → 0.2.1 functional
- 24 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Server version: 0.1.7 → 0.1.8 functional
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 5 Nov 2026 · Probed https://cpsc-recalls.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 995a30681ab772540e934241ca1d576c |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| 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 secure
Validation of cpsc-recalls.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| cpsc-recalls.caseyjhand.com. | Verified address RRset verified with the apex keys |
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=63072000; 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://cpsc-recalls.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://cpsc-recalls.caseyjhand.com/mcp | HTTPS enforced | 301 | https://cpsc-recalls.caseyjhand.com/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 →
cpsc_get_recall Get CPSC Recall Detail ~201
Fetch the full record for one CPSC recall by recall number: hazard description, remedy instructions, every product variant, UPCs, incident and injury reports, images, and the official CPSC recall page URL. Get a recall number from cpsc_search_recalls or cpsc_get_recent. CPSC jurisdiction: consumer products, including child-resistant packaging for drugs and supplements, ATVs and snowmobiles, bicycle tires, and gun safes and locks; food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF) belong to other agencies.
| Name | Type | Req | Description |
|---|---|---|---|
| recall_number | string | yes | CPSC recall number: 5 digits, e.g. "25043", with a letter a–d on some 1998–2001 records, e.g. "99003a". Get one from cpsc_search_recalls or cpsc_get_recent results. |
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_contact | string|null | – | Contact information for claiming the remedy. Null when not provided. |
| coordinated_recalls | array | – | URLs of coordinated recalls by other agencies (e.g., Canada Health). |
| cpsc_jurisdiction | string | – | Which products CPSC covers, including those near the lines of other agencies, and which agencies own food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), an… |
| cpsc_url | string | – | Official CPSC recall page — authoritative source for consumers. |
| data_quality_notes | array | – | Gaps this server observed in the CPSC record — absent description, absent hazard text, absent product entries. Derived from which fields CPSC left empty, not from any judgement about the recall itsel… |
| description | string|null | – | Full recall description including product identification details. Model numbers are typically embedded here, not in a structured field. Null when CPSC published the record without a description — rar… |
| distributors | array | – | Distributor company names. |
| error | object | – | Present when the call failed. Absent on success. |
| hazards | array | – | Hazards — read this first. |
| images | array | – | Product and identification images from the recall notice. |
| importers | array | – | Importer company names. |
| injuries | string | – | Injury and incident report narrative, e.g. "None reported" or incident count. |
| last_updated | string | – | Date last published, ISO 8601. |
| manufacturer_countries | array | – | Countries of manufacture. |
| manufacturers | array | – | Manufacturer names (often empty — see importers). |
| products | array | – | Products covered. A recall may include multiple products. Model numbers are often in the description text, not a structured field. |
| recall_date | string | – | Date issued, ISO 8601. |
| recall_number | string | – | Recall identifier. |
| remedy_instructions | string | – | Full remedy instructions — exactly what a consumer should do and how to claim. |
| remedy_options | array | – | Remedy types available: Refund, Repair, Replace, New Instructions, Dispose, Label, No Remedy Available, Inspect. Often empty — CPSC classified the remedy on fewer than half its records. Read remedy_i… |
| retailers | array | – | Retailer names with sale date ranges and price. |
| source_note | string | – | Provenance caveat: recall fields are CPSC record text with HTML markup and character codes converted to plain text, not otherwise edited or verified; check cpsc_url before a consumer-facing decision. |
| title | string | – | Official recall title. |
| upcs | array | – | UPC codes for this recall (sparse — ~4% of records have UPCs). CPSC lists UPCs for the recall as a whole, not per product, so on a recall covering several products a UPC cannot be tied to one of them. |
No examples provided.
cpsc_get_recent Get Recent CPSC Recalls ~392
Fetch the most recent CPSC consumer product recalls, newest-first, from a window of the last N days (default 30, up to 365). Use for "what's been recalled lately?" or a product safety feed; to find recalls by product, brand, hazard, or an older date range, use cpsc_search_recalls. Page past limit with offset: narrowing days cannot page, because the window is anchored to today and shrinking it drops the oldest recalls rather than advancing past the newest. A page returns fewer than limit recalls when it reaches the 64,000-byte response size budget; has_more and the notice give the offset to continue from. Pass a recall_number to cpsc_get_recall for the full record. CPSC jurisdiction: consumer products, including child-resistant packaging for drugs and supplements, ATVs and snowmobiles, bicycle tires, and gun safes and locks; food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF) belong to other agencies.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days from today. Defaults to 30. Use 7 for a weekly digest, 90 for a quarterly review. |
| limit | integer | – | Maximum number of recalls to return. Defaults to 20. A page holds at most 100: a larger limit, up to 10,000, returns 100 with a notice giving the offset to continue from. A page returns fewer when it… |
| offset | integer | – | Skip this many recalls in the window before returning results. To page through total_found, raise offset by the number of recalls the previous page returned — limit, unless that page reached the resp… |
| Name | Type | Req | Description |
|---|---|---|---|
| cpsc_jurisdiction | string | – | Which products CPSC covers, including those near the lines of other agencies, and which agencies own food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), an… |
| error | object | – | Present when the call failed. Absent on success. |
| has_more | boolean | – | True when recalls remain past this window — call again with offset raised by the number of recalls returned. |
| notice | string | – | Present when the page needs explaining: a window with no recalls (with a larger days to try), an offset past the last recall, a page cut short by the response size budget, or a page held to 100 recal… |
| offset | number | – | Number of recalls skipped before this window. |
| period | object | – | Date range queried. |
| recalls | array | – | Recent recalls, newest-first. |
| source_note | string | – | Provenance caveat: recall fields are CPSC record text with HTML markup and character codes converted to plain text, not otherwise edited or verified; check cpsc_url before a consumer-facing decision. |
| total_found | number | – | Total recalls in this period, counted before offset, limit, and the response size budget narrow the window. |
| truncated | boolean | – | True when recalls in the window remain past this page — always equal to has_more. |
No examples provided.
cpsc_search_recalls Search CPSC Recalls ~1,341
Search consumer product recalls from the CPSC (Consumer Product Safety Commission) — toys, electronics, furniture, appliances, children's products, tools, and clothing. Give at least one text filter or date bound; to browse the latest recalls without one, use cpsc_get_recent. Filters combine with AND, and a text filter matches records whose field contains every one of its words, in any order — each word as a case-insensitive substring with no stemming, so "fire" also matches fireworks and "battery" misses batteries; search a stem instead ("batter" finds battery and batteries). Start with title_search when you have a product in hand — CPSC titles carry the brand, product, and hazard phrasing. For hazard types ("fire", "choking", "burn"), use hazard_search, which matches hazard descriptions, product names, and remedy instructions. When manufacturer finds nothing, try importer, retailer, or distributor: many recalls name one of those as the responsible company. Page past limit with offset — total_found counts every match and has_more says whether more remain; a page returns fewer than limit recalls when it reaches the 64,000-byte response size budget. Pass a recall_number to cpsc_get_recall for the full record, including the complete description, all images, and incident reports. CPSC jurisdiction: consumer products, including child-resistant packaging for drugs and supplements, ATVs and snowmobiles, bicycle tires, and gun safes and locks; food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), and firearms (ATF) belong to other agencies.
| Name | Type | Req | Description |
|---|---|---|---|
| date_end | – | – | Include only recalls on or before this date. ISO 8601 format: "YYYY-MM-DD". Must be a real calendar date, and on or after date_start. |
| date_start | – | – | Include only recalls on or after this date. ISO 8601 format: "YYYY-MM-DD". Must be a real calendar date — "2026-02-31" and "2026-99-99" are rejected. |
| description_search | string | – | Keyword search within the recall description only — not the title, hazard text, or remedy instructions; matches descriptions containing every word, in any order, each as a case-insensitive substring… |
| distributor | string | – | Distributor company name, e.g. "Walmart", "Costco". Matches recalls whose distributor names contain every word, in any order, each as a case-insensitive substring with no stemming — a role distinct f… |
| hazard_search | string | – | Hazard or safety-concept keyword, e.g. "fire", "choking", "burn", "tip-over dresser". Matches when every word appears in the hazard descriptions, product names, or remedy instructions — each word in… |
| importer | string | – | Importer company name. Matches recalls whose importer names contain every word, in any order, each as a case-insensitive substring with no stemming. Use when searching for recalls by the company that… |
| limit | integer | – | Maximum number of recalls to return on this page. Defaults to 20. A page holds at most 200: a larger limit, up to 10,000, returns 200 with a notice giving the offset to continue from. A page returns… |
| manufacturer | string | – | Manufacturer name, e.g. "Samsung", "LEGO". Matches recalls whose manufacturer names contain every word, in any order, each as a case-insensitive substring with no stemming. Many recalls name the impo… |
| offset | integer | – | Skip this many matching records before returning results. To page through total_found, raise offset by the number of recalls the previous page returned — limit, unless that page reached the response… |
| product_name | string | – | Product name to search for, e.g. "crib", "space heater", "bicycle". Matches recalls whose product names contain every word, in any order, each as a case-insensitive substring with no stemming — parti… |
| remedy | string | – | Keyword search within the free-text remedy instructions, e.g. "repair", "refund", "firmware update"; matches instructions containing every word, in any order, each as a case-insensitive substring wit… |
| retailer | string | – | Retailer name, e.g. "Walmart", "Target", "Amazon". Matches recalls whose retailer text (store name, dates sold, and price) contains every word, in any order, each as a case-insensitive substring with… |
| title_search | string | – | Keyword search within the recall title, e.g. "chandelier", "space heater", "Graco crib". Matches titles containing every word, in any order, each as a case-insensitive substring with no stemming. CPS… |
| updated_end | – | – | Include only recalls last published by CPSC on or before this date. ISO 8601 format: "YYYY-MM-DD". Must be a real calendar date, and on or after updated_start. |
| updated_start | – | – | Include only recalls last published by CPSC on or after this date. ISO 8601 format: "YYYY-MM-DD". A separate axis from date_start: a 2003 recall re-published in 2025 matches updated_start "2025-01-01… |
| Name | Type | Req | Description |
|---|---|---|---|
| cpsc_jurisdiction | string | – | Which products CPSC covers, including those near the lines of other agencies, and which agencies own food and drugs (FDA), on-road vehicles and their tires (NHTSA), boats (USCG), pesticides (EPA), an… |
| effectiveQuery | string | – | The search criteria as applied, joined with AND: each non-blank text filter trimmed, the hazard alias resolved to hazard_search, and blank date bounds dropped. |
| error | object | – | Present when the call failed. Absent on success. |
| has_more | boolean | – | True when records remain past this window — call again with offset raised by the number of recalls returned. |
| notice | string | – | Present when the page needs explaining: zero matches (with which criterion to relax), an offset past the last match, a page cut short by the response size budget, or a page held to 200 recalls under… |
| offset | number | – | Number of matching records skipped before this window. |
| recalls | array | – | Matching recalls, ordered newest-first. |
| source_note | string | – | Provenance caveat: recall fields are CPSC record text with HTML markup and character codes converted to plain text, not otherwise edited or verified; check cpsc_url before a consumer-facing decision. |
| total_found | number | – | Total matching records, counted after every filter is applied and before offset, limit, and the response size budget narrow the window. |
| truncated | boolean | – | True when matching records remain past this page — always equal to has_more. |
No examples provided.
How do I install the io.github.cyanheads/cpsc-recalls-mcp-server server?
io.github.cyanheads/cpsc-recalls-mcp-server is a hosted endpoint at https://cpsc-recalls.caseyjhand.com/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 · cpsc-recalls.caseyjhand.com
claude mcp add --transport http cyanheads-cpsc-recalls-mcp-server 'https://cpsc-recalls.caseyjhand.com/mcp'
What is the io.github.cyanheads/cpsc-recalls-mcp-server server?
io.github.cyanheads/cpsc-recalls-mcp-server is listed in the public MCP registry as io.github.cyanheads/cpsc-recalls-mcp-server. US consumer product recalls from the CPSC: hazards, remedies, and affected products. This page covers its hosted endpoint (https://cpsc-recalls.caseyjhand.com/mcp).
Is the io.github.cyanheads/cpsc-recalls-mcp-server server safe to use?
io.github.cyanheads/cpsc-recalls-mcp-server scores 88 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 io.github.cyanheads/cpsc-recalls-mcp-server server expose?
io.github.cyanheads/cpsc-recalls-mcp-server exposes 3 tools: cpsc_search_recalls, cpsc_get_recall, cpsc_get_recent. Their descriptions and schemas cost roughly 1,934 tokens of context every time the server is loaded.
Does the io.github.cyanheads/cpsc-recalls-mcp-server server require authentication?
No. We connected to io.github.cyanheads/cpsc-recalls-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/cpsc-recalls-mcp-server server still maintained?
io.github.cyanheads/cpsc-recalls-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.