# China Recalls (npm · @pipeworx/mcp-china-recalls)

china-recalls: product recall announcements published by China's State Administration for Market…

- Trust score: 78/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-china-recalls/china-recalls-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-china-recalls/china-recalls-mcp)
- npm · `@pipeworx/mcp-china-recalls`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls.md), [page](https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-china-recalls`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 71/100
  - Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-china-recalls).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 365 tokens (~182/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the China Recalls MCP server?

China Recalls runs locally as an npm package, launched with npx -y @pipeworx/mcp-china-recalls. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-china-recalls -- npx -y @pipeworx/mcp-china-recalls
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-china-recalls": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-china-recalls"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-china-recalls": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-china-recalls"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-china-recalls -- npx -y @pipeworx/mcp-china-recalls
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-china-recalls": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-china-recalls"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-china-recalls --command npx --arg -y --arg @pipeworx/mcp-china-recalls
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-china-recalls:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-china-recalls"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-china-recalls": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-china-recalls"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-china-recalls -t stdio -c npx -a -y @pipeworx/mcp-china-recalls
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-china-recalls": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-china-recalls"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, −4)

- [security regression] Provenance: pass → unverified

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 81, +1)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (2)

### `china_search_recalls` (~208 tokens)

Search product recall announcements from the State Administration for Market Regulation (SAMR), China: about 1,400 announcements since 2018, newest first. Mostly motor vehicles and motorcycles, plus some consumer goods (power banks, vacuum flasks). Filter by title text (Chinese company or product, some English brands), inferred category, and date range. Returns id, title, date and category; pass an id to china_get_recall for the full notice.

Input parameters:

- `category` (string): Inferred from the title. Default all.
- `from` (string): Earliest announcement date, YYYY-MM-DD.
- `limit` (number): 1-50, default 20.
- `offset` (number): Skip this many matches, for paging.
- `query` (string): Text in the announcement title, e.g. 特斯拉, 充电宝, 小米, or tesla / power bank.
- `to` (string): Latest announcement date, YYYY-MM-DD.

### `china_get_recall` (~102 tokens)

One SAMR recall announcement in full: recalling company, units affected, production window, defect and remedy text, issuing unit, publication time and attachments (e.g. the recall plan PDF). Takes the id returned by china_search_recalls. Text is in Chinese.

Input parameters:

- `id` (string, required): Announcement id from china_search_recalls, e.g. 2025/art_473b221b409943889be9864d21a2b870.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the China Recalls MCP server?

China Recalls is an MCP server listed in the public MCP registry as io.github.pipeworx-io/china-recalls. china-recalls: product recall announcements published by China's State Administration for Market… This page covers its npm package (@pipeworx/mcp-china-recalls).

### Is the China Recalls MCP server safe to use?

China Recalls scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 China Recalls MCP server expose?

China Recalls exposes 2 tools: china_search_recalls, china_get_recall. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.

### Is the China Recalls MCP server still maintained?

China Recalls 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.

### What licence is the China Recalls MCP server under?

China Recalls declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-china-recalls
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-china-recalls
- Repository: https://github.com/pipeworx-io/mcp-china-recalls
- Website: https://pipeworx.io/packs/china-recalls
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-china-recalls/pipeworx-mcp-china-recalls