China Medical Device Lookup

io.github.huangjunsong404-cryptoPublished by GitHub account huangjunsong404-cryptov1.0.0Updated Oct 24, 2026

Look up medical devices in China by UDI, product name, registrant, registration number or category.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant look up Chinese medical device records by UDI, product name, registrant, registration number, or category.

What you can do
This remote MCP server provides lookup of medical devices registered in China. According to its description, searches can be made by UDI, product name, registrant, registration number, or category. No individual tools are listed in the supplied material, so the exact query and result formats are not documented here.
When to use it
Useful when an assistant needs to identify or verify a medical device sold or registered in China, for example checking a UDI, a registration number, or which devices a given registrant or category covers.
Requirements
A remote streamable HTTP endpoint at the provider's address; no package installation is needed. No authentication, environment variables, or headers are declared, so no credentials appear to be required.
Before you install
The server is operated by a third party, so lookup terms and any identifiers you submit are sent to that provider. No authentication is declared, which means the endpoint is open and its data provenance, accuracy, and update frequency are not documented in the supplied material. Verify results against official regulatory sources before relying on them.

Installation

In SourceWeft

  1. Open China Medical Device Lookup in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.huangjunsong404-crypto%2Fchina-medical-device-lookup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "china-medical-device-lookup": {
      "type": "http",
      "url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.