@pipeworx/china-medical-devices

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/china-medical-devices’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

China’s medical-device Unique Device Identification (UDI) register — search by product/trade name or model, resolve one device identifier, look up a manufacturer, and list what changed since a date, refreshed from the publisher’s release files.

Tools

• udi_search(query, manufacturer?, limit?) — free-text search over product name, trade name, and model (all terms must match), optionally filtered by registrant/manufacturer name.
• udi_resolve(udi_di) — exact lookup of one product-level UDI-DI.
• udi_manufacturer(name?, registrant_id?, limit?) — registrants matching a name or unified social credit code, with how many device identifiers and registration numbers each holds.
• udi_recent_changes(since, limit?) — devices whose latest published version is on or after a date, newest first, drawn from the publisher’s delta release files.
• udi_coverage() — device count, newest/oldest dates, and whether the search indexes are built yet. Check this before trusting udi_search latency on a very broad term.

Auth

Keyless. No vendor key is involved — the data lives in Pipeworx’s own store, loaded from the publisher’s own release files.

Data sources

• NMPA (National Medical Products Administration), Unique Device Identification database — the official register of medical-device Unique Device Identifiers for devices sold in China. The publisher distributes this as periodic bulk release files (a full release plus delta files), not a public query API, so this pack is refreshed on that cadence rather than calling the publisher per request. The exact release/delta routes live only in src/index.ts and scripts/nmpa-udi-load.py.

Licence note: the publisher’s download page carries only a copyright line (版权所有：国家药品监督管理局); no explicit reuse terms were found on it or in the release files themselves. Under the standing rule for a source that only publishes bulk files and is silent on reuse (hold only when terms forbid redistribution; build and flag when they are silent), this pack ships with that flag rather than a hold. If explicit terms forbidding redistribution turn up later, this needs to be revisited.

What is deliberately not stored: registrants’ contact details (e-mail, phone) the release carries — personal data this pack has no reuse ruling to serve — and packaging/carton-level identifiers, a different register at a different grain nobody has asked for. A lookup for one of those resolves found: false with a note, not an error.

Demand status: this pack was built from a standing Bruce ask to assess China-source coverage (2026-10-21), not from measured demand — the 30-day miss log showed zero misses for this specific register at the time it was proposed. Build-to-see-what-it-does, not a backlog item that real traffic was waiting on.

Cross-link: @pipeworx/china-pharma covers NMPA drug approvals and policy announcements (via HKEX disclosure filings and the NMPA English-language announcements) — a different register, drugs rather than devices, at a different grain. Use that pack for drug approvals; use this one for device identifiers.

Data and refresh

The register is loaded from the publisher’s full release and kept current by applying its delta files (daily, weekly, monthly) in date order. The loader is resumable and idempotent: a stored device is only replaced by a version that is not older. Every response carries data_as_of (the release date of the latest file applied) and, for udi_resolve / udi_coverage, ingested_at.

Individuals are not served. Some registrants are sole proprietors filing in their own name (the published registrant name is just a personal name). Their registrant name, English name and credit code are withheld at load and never stored; the device record itself (name, model, registration number) is served. udi_manufacturer therefore lists companies only.

Search speed. udi_search and udi_manufacturer scan the table until the search indexes are built (a separate database step run after the bulk load); until then expect roughly 10-15 seconds on a broad term.

Tools

• udi_search — Search China’s medical-device Unique Device Identification register by product name, trade name, or model, refreshed from the publisher’s release files. Optionally filter by registrant (manufacturer)
• udi_resolve — Resolve one China medical-device Unique Device Identifier (UDI-DI) to its registered product record — name, model, classification, registrant, and registration number.
• udi_manufacturer — Look up a medical-device registrant (manufacturer) in China’s UDI register by name or unified social credit code, and see how many device identifiers and registration numbers it holds.
• udi_recent_changes — Devices in China’s medical-device UDI register whose latest published version is on or after a given date, newest first — drawn from the publisher’s delta (daily/weekly/monthly) release files.
• udi_coverage — Coverage of China’s medical-device UDI register: device count, the full release and latest delta applied, and the data_as_of date. Registrant identity is withheld for individual (natural-person) regis