@cyanheads/cpsc-recalls-mcp-server 0.1.1

package/README.md

@@ -0,0 +1,266 @@
+<div align="center">
+  <h1>@cyanheads/cpsc-recalls-mcp-server</h1>
+  <p><b>Search and retrieve US consumer product recalls from the CPSC (Consumer Product Safety Commission) via MCP. STDIO or Streamable HTTP.</b>
+  <div>3 Tools</div>
+  </p>
+</div>
+
+<div align="center">
+
+[![Version](https://img.shields.io/badge/Version-0.1.1-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/cpsc-recalls-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^1.29.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/cpsc-recalls-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/cpsc-recalls-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^5.9.3-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.3.0+-blueviolet.svg?style=flat-square)](https://bun.sh/)
+
+</div>
+
+<div align="center">
+
+[![Install in Claude Desktop](https://img.shields.io/badge/Install_in-Claude_Desktop-D97757?style=for-the-badge&logo=anthropic&logoColor=white)](https://github.com/cyanheads/cpsc-recalls-mcp-server/releases/latest/download/cpsc-recalls-mcp-server.mcpb) [![Install in Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=cpsc-recalls-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBjeWFuaGVhZHMvY3BzYy1yZWNhbGxzLW1jcC1zZXJ2ZXIiXX0=) [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Server-0098FF?style=for-the-badge&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22cpsc-recalls-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40cyanheads%2Fcpsc-recalls-mcp-server%22%5D%7D)
+
+[![Framework](https://img.shields.io/badge/Built%20on-@cyanheads/mcp--ts--core-67E8F9?style=flat-square)](https://www.npmjs.com/package/@cyanheads/mcp-ts-core)
+
+</div>
+
+---
+
+## Tools
+
+3 tools for searching and retrieving CPSC consumer product recall data:
+
+| Tool | Description |
+|:---|:---|
+| `cpsc_search_recalls` | Search consumer product recalls by product name, brand, retailer, importer, or description keyword, with optional date filtering |
+| `cpsc_get_recall` | Full detail for a single recall by recall number — hazards, remedy, products, injuries, images, and the official CPSC page |
+| `cpsc_get_recent` | Fetch the most recent recalls ordered newest-first, scoped to a configurable date window |
+
+**CPSC jurisdiction:** Consumer products only — toys, electronics, furniture, appliances, children's products, tools, and clothing. Food and drugs (FDA), motor vehicles and tires (NHTSA), boats (USCG), and pesticides (EPA) are not in this database. Every response includes a jurisdiction note.
+
+Data sourced from the [U.S. Consumer Product Safety Commission](https://www.saferproducts.gov/) via the CPSC public recalls API.
+
+### `cpsc_search_recalls`
+
+Search recalls with flexible filtering across product, organization, and description fields.
+
+- Filter by product name, manufacturer, retailer, importer, or description keyword — all fields are optional substring matches that combine with AND
+- Date range filtering via `date_start` / `date_end` (ISO 8601)
+- Client-side limit (1–200, default 20) applied after fetching all matching records
+- Returns hazard descriptions, remedy options, remedy instructions, product list, UPCs, manufacturer/importer/retailer names, images, and the CPSC recall page URL
+- Includes `total_found` and `truncated` fields for pagination awareness
+- Note: the `Hazard` filter param is non-functional in the upstream API — use `description_search` for hazard-type keywords like "fire", "choking", or "burn"
+- When `manufacturer` returns no results, try `importer` or `retailer` — many recalls list the importer as the primary organization
+
+---
+
+### `cpsc_get_recall`
+
+Full detail for a single CPSC recall by recall number.
+
+- Accepts modern 5-digit recall numbers (e.g. `"25043"`) and historical 1998–2001 records with letter suffixes (e.g. `"99003a"`)
+- Returns the complete record: full description, all hazard descriptions, remedy type and instructions, all product variants with unit counts, UPCs, incident/injury narrative, manufacturer and importer names, retailer names with sale date ranges, country of manufacture, images, and coordinated agency recall URLs
+- Model numbers are typically embedded in the description text, not in a structured field
+- Use `cpsc_search_recalls` or `cpsc_get_recent` to find a recall number first
+
+---
+
+### `cpsc_get_recent`
+
+Fetch the most recent CPSC recalls, ordered newest-first.
+
+- Configurable look-back window of 1–365 days (default 30)
+- Limit of 1–100 results (default 20)
+- Always applies a date window — without one, the upstream API returns 9,800+ records
+- Returns a lightweight record per recall: number, date, title, hazards, remedy types, product names, and CPSC URL
+- Use `cpsc_get_recall` to retrieve full detail for any result
+
+## Features
+
+Built on [`@cyanheads/mcp-ts-core`](https://github.com/cyanheads/mcp-ts-core):
+
+- Declarative tool definitions — single file per tool, framework handles registration and validation
+- Unified error handling — handlers throw, framework catches, classifies, and formats
+- Pluggable auth: `none`, `jwt`, `oauth`
+- Swappable storage backends: `in-memory`, `filesystem`, `Supabase`, `Cloudflare KV/R2/D1`
+- Structured logging with optional OpenTelemetry tracing
+- STDIO and Streamable HTTP transports
+
+CPSC-specific:
+
+- Full integration with the CPSC saferproducts.gov public recalls API
+- Client-side filtering applied over complete API result sets for accurate `total_found` counts
+- Jurisdiction boundary documented in every response — prevents misattribution of food, vehicle, or drug recalls
+
+Agent-friendly output:
+
+- Jurisdiction note on every response — agents can route callers to the correct agency (FDA, NHTSA, USCG, EPA) when the product is out of scope
+- `total_found` + `truncated` fields on search/recent responses — agents can detect when results are clipped and suggest narrowing filters
+- `cpsc_url` on every recall — authoritative source link for consumer verification
+
+## Getting started
+
+Add the following to your MCP client configuration file.
+
+```json
+{
+  "mcpServers": {
+    "cpsc-recalls": {
+      "type": "stdio",
+      "command": "bunx",
+      "args": ["@cyanheads/cpsc-recalls-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with npx (no Bun required):
+
+```json
+{
+  "mcpServers": {
+    "cpsc-recalls": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@cyanheads/cpsc-recalls-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with Docker:
+
+```json
+{
+  "mcpServers": {
+    "cpsc-recalls": {
+      "type": "stdio",
+      "command": "docker",
+      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/cpsc-recalls-mcp-server:latest"]
+    }
+  }
+}
+```
+
+For Streamable HTTP, set the transport and start the server:
+
+```sh
+MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
+# Server listens at http://localhost:3010/mcp
+```
+
+### Prerequisites
+
+- [Bun v1.3.0](https://bun.sh/) or higher (or Node.js v24+).
+- No API key required — the CPSC public recalls API is freely accessible.
+
+### Installation
+
+1. **Clone the repository:**
+
+```sh
+git clone https://github.com/cyanheads/cpsc-recalls-mcp-server.git
+```
+
+2. **Navigate into the directory:**
+
+```sh
+cd cpsc-recalls-mcp-server
+```
+
+3. **Install dependencies:**
+
+```sh
+bun install
+```
+
+4. **Configure environment:**
+
+```sh
+cp .env.example .env
+# edit .env if needed — no required API keys
+```
+
+## Configuration
+
+All configuration is validated at startup via Zod schemas. Key environment variables:
+
+| Variable | Description | Default |
+|:---|:---|:---|
+| `MCP_TRANSPORT_TYPE` | Transport: `stdio` or `http` | `stdio` |
+| `MCP_HTTP_PORT` | HTTP server port | `3010` |
+| `MCP_HTTP_HOST` | HTTP server host | `127.0.0.1` |
+| `MCP_HTTP_ENDPOINT_PATH` | HTTP endpoint path | `/mcp` |
+| `MCP_PUBLIC_URL` | Public origin for TLS-terminating reverse-proxy deployments | — |
+| `MCP_AUTH_MODE` | Authentication: `none`, `jwt`, or `oauth` | `none` |
+| `MCP_LOG_LEVEL` | Log level (`debug`, `info`, `warning`, `error`) | `info` |
+| `LOGS_DIR` | Directory for log files (Node.js only) | `<project-root>/logs` |
+| `STORAGE_PROVIDER_TYPE` | Storage backend: `in-memory`, `filesystem`, `supabase`, `cloudflare-kv/r2/d1` | `in-memory` |
+| `OTEL_ENABLED` | Enable OpenTelemetry | `false` |
+
+No server-specific API keys are required. See [`.env.example`](./.env.example) for the full list of optional overrides.
+
+## Running the server
+
+### Local development
+
+- **Build and run the production version:**
+
+  ```sh
+  # One-time build
+  bun run rebuild
+
+  # Run the built server
+  bun run start:stdio
+  # or
+  bun run start:http
+  ```
+
+- **Run checks and tests:**
+
+  ```sh
+  bun run devcheck  # Lint, format, typecheck, security
+  bun run test      # Vitest test suite
+  ```
+
+### Docker
+
+```sh
+docker build -t cpsc-recalls-mcp-server .
+docker run --rm -p 3010:3010 cpsc-recalls-mcp-server
+```
+
+The Dockerfile defaults to HTTP transport, stateless session mode, and logs to `/var/log/cpsc-recalls-mcp-server`. OpenTelemetry peer dependencies are installed by default — build with `--build-arg OTEL_ENABLED=false` to omit them.
+
+## Project structure
+
+| Directory | Purpose |
+|:---|:---|
+| `src/index.ts` | `createApp()` entry point — registers tools and inits the CPSC service |
+| `src/mcp-server/tools` | Tool definitions (`*.tool.ts`). Three tools: search, get-recall, get-recent |
+| `src/services/cpsc-recall` | CPSC recall service — API client, types, normalization |
+
+## Development guide
+
+See [`CLAUDE.md`](./CLAUDE.md) / [`AGENTS.md`](./AGENTS.md) for development guidelines and architectural rules. The short version:
+
+- Handlers throw, framework catches — no `try/catch` in tool logic
+- Use `ctx.log` for request-scoped logging, `ctx.state` for tenant-scoped storage
+- Register new tools in the `createApp()` arrays in `src/index.ts`
+- Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields
+
+## Contributing
+
+Issues and pull requests are welcome. Run checks and tests before submitting:
+
+```sh
+bun run devcheck
+bun run test
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE) for details.

package/changelog/0.1.x/0.1.0.md

@@ -0,0 +1,11 @@
+---
+summary: "Initial release — CPSC recall search, details, and product lookup via MCP"
+breaking: false
+security: false
+---
+
+# 0.1.0 — 2026-05-31
+
+## Added
+
+- Initial scaffold from `@cyanheads/mcp-ts-core` template

package/changelog/0.1.x/0.1.1.md

@@ -0,0 +1,26 @@
+---
+summary: "Initial public release — cpsc_search_recalls, cpsc_get_recall, cpsc_get_recent over the CPSC saferproducts.gov API"
+breaking: false
+security: true
+---
+
+# 0.1.1 — 2026-06-01
+
+Initial public release. Search and retrieve US consumer product recalls from the CPSC via the saferproducts.gov API.
+
+## Added
+
+- **`cpsc_search_recalls`** — search recalls by product name, brand, retailer, importer, or description keyword; optional date window and result limit.
+- **`cpsc_get_recall`** — full recall detail by recall number: hazards, remedy options, affected products, consumer contact.
+- **`cpsc_get_recent`** — recent recalls feed by date window, defaulting to the past 30 days.
+- **`manifest.json`** — MCPB bundle support for one-click Claude Desktop install.
+- Plugin manifests (`.claude-plugin/`, `.codex-plugin/`) populated with package metadata, descriptions, and install config.
+
+## Fixed
+
+- **`ctx.fail` call sites** — error `cause` moved to the correct fourth argument position across all three tool handlers; was incorrectly merged into the third (options) argument.
+- **`cpsc_get_recall` hazard mapping** — filter applied before map to avoid emitting objects with empty `description`; was mapping then filtering.
+
+## Security
+
+- **`date_start` / `date_end` input validation** — date fields in `cpsc_search_recalls` now enforce ISO 8601 `YYYY-MM-DD` format via `z.regex()`, surfacing as a `pattern` constraint in the JSON Schema. Previously accepted any string and passed it unvalidated to the upstream API.

package/changelog/template.md

@@ -0,0 +1,127 @@
+---
+# FORMAT REFERENCE — do not edit. Copy this file to
+# `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.8.x/0.8.6.md`)
+# to author a new release. Set that file's H1 to `# <version> — YYYY-MM-DD`
+# with a concrete date.
+
+# Required. One-line GitHub Release-style headline. 350 character cap.
+# Default short and scannable. Don't pad, don't stitch unrelated changes with
+# semicolons — pick the headline. Quotes required: unquoted YAML treats `: `
+# inside the value as a key separator and fails GitHub's strict parser.
+summary: ""
+
+# Set `true` when consumers must change code to upgrade: API removals,
+# signature changes, config renames, behavior changes that break existing
+# usage. Flagged as `Breaking` in the rollup.
+breaking: false
+
+# Set `true` if this release contains any security fix. Pairs with the
+# `## Security` section below. Flagged as `Security` in the rollup so
+# users can triage upgrade urgency at a glance.
+security: false
+
+# Optional free-form notes for maintenance agents processing this release.
+# Not rendered in CHANGELOG — consumed by agents running `maintenance` on
+# downstream servers. Use for adoption instructions that don't fit the
+# human-facing sections: new files to create, fields to populate, one-time
+# migration steps. Omit the field entirely when there's nothing to say.
+# agent-notes: |
+#   <instructions for downstream maintenance agents>
+---
+
+# <version> — YYYY-MM-DD
+
+<!--
+  AUTHORING GUIDE — applies to the new per-version file you create from this
+  template.
+
+  Audience: someone scanning release notes to decide what affects them. Lead
+  each bullet with the symbol or concept name in **bold** so they can skip
+  what's irrelevant and zoom in on what's not.
+
+  Tone: terse, fact-dense, not verbose. Default to one sentence per bullet —
+  name the symbol, state what changed, stop. Use a second sentence only when
+  it carries weight. If a bullet feels long, it is.
+
+  Cut: mechanism walkthroughs (those belong in JSDoc, CLAUDE.md/AGENTS.md, or the
+  relevant skill), ceremonial framings ("This release introduces…",
+  backwards-compat paragraphs), file-by-file test enumerations, internal
+  implementation notes. Prefer code/symbol names over English re-explanations.
+
+  Narrative intro: skip by default. Add one short sentence only when the
+  release theme genuinely needs framing the bullets can't carry.
+
+  Sections: Keep a Changelog order — Added, Changed, Deprecated, Removed,
+  Fixed, Security. Include only sections with entries; delete the rest
+  (including the commented-out scaffolding below). Don't ship empty headers.
+
+  Include: every distinct fact a reader needs to adopt or audit the release —
+  new exports, signatures, lint rule IDs, env vars, breaking changes, version
+  bumps on shipped skills. Nothing more.
+
+  Links: link issues, PRs, docs, or skills where they help a reader jump to
+  context. Once per item per entry — don't re-link the same issue in summary,
+  narrative, and bullet. Skip links for inline symbol names; code spans speak
+  for themselves.
+
+  Issue/PR URLs: use full URLs. GitHub's bare `#NN` auto-link only resolves
+  inside its own UI, not in npm reads or local editors.
+
+      [#38](https://github.com/cyanheads/mcp-ts-core/issues/38)   ← issue
+      [#42](https://github.com/cyanheads/mcp-ts-core/pull/42)     ← PR
+
+  Verify numbers exist before linking (`gh issue view NN`, `gh pr view NN`).
+  Never speculate on a future number — `#42` for an upcoming PR silently
+  resolves to whatever real item already owns 42, and timeline previews pull
+  in that unrelated item's metadata.
+
+  TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
+  via `gh release create --notes-from-tag`. The tag is a derivative of this
+  changelog entry — a condensed, scannable version, not a copy. Format:
+
+    <theme — omit version number, GitHub prepends it>
+                                                          ← blank line
+    <1-2 sentence context: what this release does>
+                                                          ← blank line
+    Dependency bumps:                                     ← section header
+                                                          ← blank line
+    - `@cyanheads/mcp-ts-core` ^0.9.1 → ^0.9.6          ← bullet
+                                                          ← blank line
+    Changed:                                              ← only sections with entries
+                                                          ← blank line
+    - `format()` output includes `query` in text mode
+                                                          ← blank line
+    Added:
+                                                          ← blank line
+    - `manifest.json` scaffolded for MCPB bundle support
+    - Install badges (Claude Desktop, Cursor, VS Code)
+                                                          ← blank line
+    <N> tests pass; `bun run devcheck` clean.             ← footer
+
+  Never a flat comma-separated string. Always structured markdown with
+  sections. The tag must scan well as a rendered GitHub Release page.
+-->
+
+## Added
+
+-
+
+## Changed
+
+-
+
+<!-- ## Deprecated
+
+- -->
+
+<!-- ## Removed
+
+- -->
+
+## Fixed
+
+-
+
+<!-- ## Security
+
+- -->

package/dist/index.d.ts

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview cpsc-recalls-mcp-server MCP server entry point.
+ * @module index
+ */
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG"}

package/dist/index.js

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview cpsc-recalls-mcp-server MCP server entry point.
+ * @module index
+ */
+import { createApp } from '@cyanheads/mcp-ts-core';
+import { cpscGetRecall } from './mcp-server/tools/definitions/cpsc-get-recall.tool.js';
+import { cpscGetRecent } from './mcp-server/tools/definitions/cpsc-get-recent.tool.js';
+import { cpscSearchRecalls } from './mcp-server/tools/definitions/cpsc-search-recalls.tool.js';
+import { initCpscRecallService } from './services/cpsc-recall/cpsc-recall-service.js';
+await createApp({
+    tools: [cpscSearchRecalls, cpscGetRecall, cpscGetRecent],
+    resources: [],
+    prompts: [],
+    instructions: 'CPSC consumer product recall database (saferproducts.gov). ' +
+        'Use cpsc_search_recalls to find recalls by product, brand, hazard, or date. ' +
+        'Use cpsc_get_recall for full detail on a specific recall number. ' +
+        'Use cpsc_get_recent for a recent recall feed. ' +
+        'CPSC jurisdiction: consumer products only — food/drugs (FDA), vehicles/tires (NHTSA), boats (USCG), pesticides (EPA) are covered by other agencies.',
+    setup(core) {
+        void core;
+        initCpscRecallService();
+    },
+});
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EAAE,aAAa,EAAE,MAAM,wDAAwD,CAAC;AACvF,OAAO,EAAE,aAAa,EAAE,MAAM,wDAAwD,CAAC;AACvF,OAAO,EAAE,iBAAiB,EAAE,MAAM,4DAA4D,CAAC;AAC/F,OAAO,EAAE,qBAAqB,EAAE,MAAM,+CAA+C,CAAC;AAEtF,MAAM,SAAS,CAAC;IACd,KAAK,EAAE,CAAC,iBAAiB,EAAE,aAAa,EAAE,aAAa,CAAC;IACxD,SAAS,EAAE,EAAE;IACb,OAAO,EAAE,EAAE;IACX,YAAY,EACV,6DAA6D;QAC7D,8EAA8E;QAC9E,mEAAmE;QACnE,gDAAgD;QAChD,qJAAqJ;IACvJ,KAAK,CAAC,IAAI;QACR,KAAK,IAAI,CAAC;QACV,qBAAqB,EAAE,CAAC;IAC1B,CAAC;CACF,CAAC,CAAC"}

package/dist/mcp-server/tools/definitions/cpsc-get-recall.tool.d.ts

@@ -0,0 +1,51 @@
+/**
+ * @fileoverview Full detail for a single CPSC recall by recall number.
+ * @module mcp-server/tools/definitions/cpsc-get-recall
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+import { JsonRpcErrorCode } from '@cyanheads/mcp-ts-core/errors';
+export declare const cpscGetRecall: import("@cyanheads/mcp-ts-core").ToolDefinition<z.ZodObject<{
+    recall_number: z.ZodString;
+}, z.core.$strip>, z.ZodObject<{
+    recall_number: z.ZodString;
+    recall_date: z.ZodString;
+    last_updated: z.ZodString;
+    title: z.ZodString;
+    description: z.ZodString;
+    cpsc_url: z.ZodString;
+    consumer_contact: z.ZodNullable<z.ZodString>;
+    hazards: z.ZodArray<z.ZodObject<{
+        description: z.ZodString;
+    }, z.core.$strip>>;
+    remedy_options: z.ZodArray<z.ZodString>;
+    remedy_instructions: z.ZodString;
+    products: z.ZodArray<z.ZodObject<{
+        name: z.ZodString;
+        units_recalled: z.ZodString;
+    }, z.core.$strip>>;
+    upcs: z.ZodArray<z.ZodString>;
+    injuries: z.ZodString;
+    manufacturers: z.ZodArray<z.ZodString>;
+    importers: z.ZodArray<z.ZodString>;
+    retailers: z.ZodArray<z.ZodString>;
+    distributors: z.ZodArray<z.ZodString>;
+    manufacturer_countries: z.ZodArray<z.ZodString>;
+    images: z.ZodArray<z.ZodObject<{
+        url: z.ZodString;
+        caption: z.ZodString;
+    }, z.core.$strip>>;
+    coordinated_recalls: z.ZodArray<z.ZodString>;
+    cpsc_jurisdiction: z.ZodString;
+}, z.core.$strip>, readonly [{
+    readonly reason: "not_found";
+    readonly code: JsonRpcErrorCode.NotFound;
+    readonly when: "No recall exists with the given recall number";
+    readonly recovery: "Verify the recall number (e.g. \"25043\" for modern records, \"99003a\" for 1998–2001 historical records). Use cpsc_search_recalls or cpsc_get_recent to find the correct number.";
+}, {
+    readonly reason: "upstream_error";
+    readonly code: JsonRpcErrorCode.ServiceUnavailable;
+    readonly when: "The saferproducts.gov API returned an error or timed out";
+    readonly recovery: "The CPSC API is occasionally unavailable. Retry in a few seconds.";
+    readonly retryable: true;
+}], undefined>;
+//# sourceMappingURL=cpsc-get-recall.tool.d.ts.map

package/dist/mcp-server/tools/definitions/cpsc-get-recall.tool.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cpsc-get-recall.tool.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/tools/definitions/cpsc-get-recall.tool.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAQ,CAAC,EAAE,MAAM,wBAAwB,CAAC;AACjD,OAAO,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AAQjE,eAAO,MAAM,aAAa;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;cA8RxB,CAAC"}