Skip to content

cpsc-recalls-mcp-server

io.github.cyanheads/cpsc-recalls-mcp-servercyanheadsstreamable-httpv0.3.2Scanned

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

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the cpsc-recalls-mcp-server can do

The cpsc-recalls-mcp-server is published by the GitHub account cyanheads. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (cpsc_get_recall).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.3.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Only reads 3Show 3 read-only tools
  • cpsc_get_recallFetch 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 offic…Reads text others writeNo findings

    Why it is in this group

    • The name "cpsc_get_recall" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • cpsc_get_recentFetch the most recent CPSC consumer product recalls, newest-first, from a window of the last N days (default 30, up to 365).No findings

    Why it is in this group

    • The name "cpsc_get_recent" says "get": a word for reading.
    Description, as the server wrote it
    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. A page holds up to 1,000 recalls. Continue by adding the number returned to offset. Narrowing days drops the oldest recalls because the window is anchored to today. 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.

    Annotations the server declares

    • readOnlyHint: true
  • cpsc_search_recallsSearch consumer product recalls from the CPSC (Consumer Product Safety Commission) — toys, electronics, furniture, appliances, children's products, tools, and clothing.No findings

    Why it is in this group

    • The name "cpsc_search_recalls" says "search": a word for reading.
    Description, as the server wrote it
    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 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. Use injury_search for incident narratives, remedy_option for a classified remedy, and upc for barcode candidates. 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 holds up to 500 recalls. Continue by adding the number returned to offset. Pass a recall_number to cpsc_get_recall for the full record, including the complete description, and all images. 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 0.3.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http cpsc-recalls https://cpsc-recalls.caseyjhand.com/mcp
claude mcp add --transport http cpsc-recalls https://cpsc-recalls.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cpsc-recalls__cpsc_search_recalls",
      "mcp__cpsc-recalls__cpsc_get_recall",
      "mcp__cpsc-recalls__cpsc_get_recent"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cpsc-recalls. Review it before you use it.

Capability tags behind 1 rule
  • mcp__cpsc-recalls__cpsc_get_recall untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/cpsc-recalls-mcp-server/verify?hash=caad02bbf6488d28a67b7d17a67ecf477b5046dfc58702e391a2f5f06115b6d1" | jq -e '.changed == false'

Pinned hash caad02bbf648, from Nov 21, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/cpsc-recalls-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/cpsc-recalls-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/cpsc-recalls-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/cpsc-recalls-mcp-server)

Source: MCP Registry · repository. Synced Nov 21, 2026, 18:17 UTC.

cpsc-recalls-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the cpsc-recalls-mcp-server safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the cpsc-recalls-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the cpsc-recalls-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the cpsc-recalls-mcp-server have?

3 tools: 3 read. cpsc_search_recalls, cpsc_get_recall and cpsc_get_recent.

Does the cpsc-recalls-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the cpsc-recalls-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the cpsc-recalls-mcp-server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.