China Recalls MCP server

@pipeworx/china-recalls

Product recall announcements published by China's State Administration for Market Regulation (SAMR): about 1,400 announcements since 2018, searchable by title, category and date, with the full notice text for each. Keyless, live per request.

Part of Pipeworx — an MCP gateway connecting AI agents to 1872+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• chinasearchrecalls(query?, category?, from?, to?, limit?, offset?) — recall announcements newest first. Returns id, title, date and an inferred category (vehicle, consumerproduct, monthlydigest). Answers "has this company or product been recalled in China, and when".
• chinagetrecall(id) — one announcement in full: recalling company, units affected, production window, defect and remedy text (Chinese), issuing unit, publication time, and attachments such as the recall-plan PDF.

Auth

Keyless.

Data sources

• State Administration for Market Regulation (SAMR), China, product recall announcements (the recall column of the SAMR government-affairs pages). Public, served without credentials. The pack proxies per call and stores nothing.

Things the next person would otherwise rediscover

• Scope is mostly vehicles. Of the listed announcements the large majority are cars and motorcycles. Consumer goods (e.g. a power bank, a vacuum flask) are a small minority. The Defective Product Administration Center site was not reachable from our vantage, so no separate consumer-goods list is covered.
• Monthly "domestic and foreign recall information" digests are listed but published as images; chinagetrecall reports image_only for them rather than inventing text.
• Titles are Chinese. query matches title text; a short alias table maps common English brand and product words (tesla, xiaomi, power bank, ...) to their Chinese forms and the terms actually used are echoed in querytermsused.
• Category is inferred from the title, not published by SAMR. Treat consumer_product as "not recognised as a vehicle".
• Dates are announcement dates, not recall start dates; many announcements are published in batches on one day. The production window and units affected are parsed from the text and are null when the notice words them differently.
• A non-empty upstream list is asserted on every call; an empty first page raises an error instead of reporting "no recalls".

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "china-recalls": {
      "url": "https://gateway.pipeworx.io/china-recalls/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/china-recalls/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Shortened. The full README is on GitHub.