Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.cyanheads/cpsc-recalls-mcp-server

REMOTE · CPSC-RECALLS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

US consumer product recalls from the CPSC — hazards, remedies, and affected products.

+5 this week 67 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1532 tokens (~510/item across 3 items; 3 tools + 0 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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · cpsc-recalls.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-cpsc-recalls-mcp-server https://cpsc-recalls.caseyjhand.com/mcp
# ~/.codex/config.toml
[mcp_servers.cyanheads-cpsc-recalls-mcp-server]
url = "https://cpsc-recalls.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-cpsc-recalls-mcp-server": {
      "type": "remote",
      "url": "https://cpsc-recalls.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-cpsc-recalls-mcp-server --url https://cpsc-recalls.caseyjhand.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-cpsc-recalls-mcp-server:
    url: "https://cpsc-recalls.caseyjhand.com/mcp"
// mcp.json
{
  "mcpServers": {
    "cyanheads-cpsc-recalls-mcp-server": {
      "type": "http",
      "url": "https://cpsc-recalls.caseyjhand.com/mcp"
    }
  }
}

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

Changelog

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.

  • 2 Aug 26 +1

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

  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

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

  • 28 Jul 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.

  • 27 Jul 26 −1
    • Tool “cpsc_search_recalls” rewrote its description, which is the text the model reads security
    • Tool “cpsc_get_recent” rewrote its description, which is the text the model reads security
    • Schema quality: 299 → 510 functional
    • Stability: unverified → 0.03 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 0.1.5 → 0.1.6 functional
    • “cpsc_search_recalls” added an optional parameter “remedy” cosmetic
    • “cpsc_search_recalls” added an optional parameter “offset” cosmetic
    • “cpsc_search_recalls” added an optional parameter “hazard_search” cosmetic
    • “cpsc_search_recalls” added an optional parameter “distributor” cosmetic
    • “cpsc_get_recent” added an optional parameter “offset” cosmetic
    • “cpsc_search_recalls” added an optional parameter “updated_start” cosmetic
    • “cpsc_search_recalls” added an optional parameter “title_search” cosmetic
    • “cpsc_search_recalls” added an optional parameter “updated_end” cosmetic
    • “cpsc_search_recalls” reworded the description of “description_search” cosmetic
  • 26 Jul 26 63

    First indexed and scored.

Diagnostics

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 3 Aug 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 7 Jul 2026 5 Oct 2026 ECDSA 256 ECDSA-SHA256 5aad900eb2055a0b0ea55912ec19680c
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
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
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
MCP tools — 3 exposed · ~1,434 tokens

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.

Tool Tokens
cpsc_get_recall ~166

Full detail for a single CPSC recall by recall number. Returns the complete record: hazard description, remedy instructions, all product variants, incident/injury reports, images, and the official CPSC recall page URL. Use after cpsc_search_recalls or cpsc_get_recent to get the full picture on a specific recall. CPSC jurisdiction: consumer products only — food, vehicles, drugs, and pesticides are covered by other agencies.

NameTypeReqDescription
recall_numberstringyesCPSC recall number. Modern records (2002–present) are 5-digit numeric, e.g. "25043". Historical records from 1998–2001 may have a letter suffix a–d, e.g. "99003a". Obtain from cpsc_search_recalls res…
NameTypeReqDescription
consumer_contactyesContact information for claiming the remedy. Null when not provided.
coordinated_recallsarrayyesURLs of coordinated recalls by other agencies (e.g., Canada Health).
cpsc_jurisdictionstringyesCPSC covers consumer products — toys, electronics, furniture, appliances, tools, clothing. Does NOT cover: food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (AT…
cpsc_urlstringyesOfficial CPSC recall page — authoritative source for consumers.
data_quality_notesarrayyesGaps this server observed in the upstream CPSC record — absent description, absent hazard text, absent product entries. Derived from which fields CPSC left empty, not from any judgement about the rec…
descriptionyesFull 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…
distributorsarrayyesDistributor company names.
hazardsarrayyesHazards — read this first.
imagesarrayyesProduct and identification images from the recall notice.
importersarrayyesImporter company names.
injuriesstringyesInjury and incident report narrative, e.g. "None reported" or incident count.
last_updatedstringyesDate last published, ISO 8601.
manufacturer_countriesarrayyesCountries of manufacture.
manufacturersarrayyesManufacturer names (often empty — see importers).
productsarrayyesProducts covered. A recall may include multiple products. Note: model numbers are often in the description text, not a structured field.
recall_datestringyesDate issued, ISO 8601.
recall_numberstringyesRecall identifier.
remedy_instructionsstringyesFull remedy instructions — exactly what a consumer should do and how to claim.
remedy_optionsarrayyesRemedy 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…
retailersarrayyesRetailer names with sale date ranges and price.
source_notestringyesProvenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision.
titlestringyesOfficial recall title.
upcsarrayyesUPC codes for this recall (sparse — ~4% of records have UPCs). UPCs are stored at the recall level in the API, not per-product; when the recall covers multiple products, UPC-to-product attribution is…

No examples provided.

cpsc_get_recent ~234

Fetch the most recent CPSC consumer product recalls, ordered newest-first. Use for "what's been recalled lately?" or a product safety feed. Always applies a date window (default: last 30 days) — without a date filter the API returns all 9,800+ records. Page past limit with offset: narrowing days cannot page, because the window is anchored to today and shrinking it drops the oldest records rather than advancing past the newest. CPSC jurisdiction: consumer products only — food, vehicles, drugs, and pesticides are covered by other agencies.

NameTypeReqDescription
daysintegerLook back this many days from today. Defaults to 30. Use 7 for a weekly digest, 90 for a quarterly review.
limitintegerMaximum number of recalls to return. Defaults to 20.
offsetintegerSkip this many recalls in the window before returning results. Combine with limit to page through total_found — e.g. limit 20 with offset 0, 20, 40. An offset at or past total_found returns an empty…
NameTypeReqDescription
cpsc_jurisdictionstringyesCPSC covers consumer products — toys, electronics, furniture, appliances, tools, clothing. Does NOT cover: food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (AT…
has_morebooleanyesTrue when recalls remain past this window — call again with offset raised by the number of recalls returned.
offsetnumberyesNumber of recalls skipped before this window.
periodobjectyesDate range queried.
recallsarrayyesRecent recalls, newest-first.
source_notestringyesProvenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision.
total_foundnumberyesTotal recalls in this period, counted before offset and limit narrow the window.
truncatedbooleanyesTrue when total_found exceeds the limit. Independent of offset.

No examples provided.

cpsc_search_recalls ~1,034

Search consumer product recalls from the CPSC (Consumer Product Safety Commission) database. Covers toys, electronics, furniture, appliances, children's products, tools, and clothing — everything under CPSC jurisdiction. Does NOT cover food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), or pesticides (EPA). All filter fields are optional substring matches that combine with AND. Start with title_search when you have a product in hand — CPSC titles carry the brand, product, and hazard phrasing. For hazard-type filtering ("fire", "choking", "burn"), use hazard_search, which matches hazard text, product names, and remedy instructions in one pass. When manufacturer returns no results, try importer, retailer, or distributor: many recalls list one of those as the primary responsible org. Page past limit with offset — total_found and has_more say where the window sits in the full result set. Use cpsc_get_recall with a recall_number from results to retrieve the full record including complete description, all images, and incident reports.

NameTypeReqDescription
date_endInclude 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_startInclude 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_searchstringKeyword search within the recall Description field only (does not search Title, Hazards, or remedy text). Use for product details not captured in product_name — model numbers, colors, sale channels.…
distributorstringDistributor company name, e.g. "Walmart", "Costco". Substring match against the Distributors array — a role distinct from retailer and importer, and populated on far fewer records.
hazard_searchstringHazard or safety-concept keyword, e.g. "fire", "choking", "burn", "laceration". Applied client-side after the upstream fetch. Matches when the term appears in any of: hazard descriptions, product nam…
importerstringImporter company name. Use when searching for recalls by the company that brought the product into the US.
limitintegerMaximum number of results to return (applied client-side — the API returns all matches). Defaults to 20.
manufacturerstringManufacturer name, e.g. "Samsung", "LEGO". Substring match against the Manufacturers array. Note: many recalls list the importer or retailer as the primary org rather than the manufacturer — try impo…
offsetintegerSkip this many matching records before returning results. Combine with limit to page through total_found — e.g. limit 20 with offset 0, 20, 40. An offset at or past total_found returns an empty resul…
product_namestringProduct name to search for, e.g. "crib", "space heater", "bicycle". Substring match — partial names work.
remedystringKeyword search within the free-text remedy instructions, e.g. "repair", "refund", "firmware update". Substring match, applied upstream. This searches the remedy narrative, not the structured remedy_o…
retailerstringRetailer name, e.g. "Walmart", "Target", "Amazon". Substring match against the retailer narrative (which includes store name, dates sold, and price).
title_searchstringKeyword search within the recall Title, e.g. "chandelier", "space heater", "inclined sleeper". Substring match. CPSC titles name the brand, the product, and the hazard, which makes this the highest-s…
updated_endInclude 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_startInclude 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…
NameTypeReqDescription
cpsc_jurisdictionstringyesCPSC covers consumer products — toys, electronics, furniture, appliances, tools, clothing. Does NOT cover: food/drugs (FDA), motor vehicles/tires (NHTSA), boats (USCG), pesticides (EPA), firearms (AT…
has_morebooleanyesTrue when records remain past this window — call again with offset raised by the number of recalls returned.
offsetnumberyesNumber of matching records skipped before this window.
recallsarrayyesMatching recalls, ordered newest-first.
source_notestringyesProvenance caveat: recall fields are relayed from CPSC unedited and unverified; check cpsc_url before a consumer-facing decision.
total_foundnumberyesTotal matching records, counted after hazard_search is applied and before offset and limit narrow the window.
truncatedbooleanyesTrue when total_found exceeds the limit. Independent of offset.

No examples provided.