# China Medical Device Lookup (remote · mcp.agentdatacore.com)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mcp.agentdatacore.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device.md), [page](https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device)

## Channel facts

- Endpoint: `https://mcp.agentdatacore.com/mcp/products/medical-device`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1460 tokens (~243/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Medical Device Lookup MCP server?

China Medical Device Lookup is a hosted endpoint at https://mcp.agentdatacore.com/mcp/products/medical-device, so there is nothing to install locally. 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 --transport http huangjunsong404-crypto-china-medical-device-look 'https://mcp.agentdatacore.com/mcp/products/medical-device'
```

### Cursor

```json
{
  "mcpServers": {
    "huangjunsong404-crypto-china-medical-device-look": {
      "url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "huangjunsong404-crypto-china-medical-device-look": {
      "type": "http",
      "url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
    }
  }
}
```

### Codex

```toml
[mcp_servers.huangjunsong404-crypto-china-medical-device-look]
url = "https://mcp.agentdatacore.com/mcp/products/medical-device"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "huangjunsong404-crypto-china-medical-device-look": {
      "type": "remote",
      "url": "https://mcp.agentdatacore.com/mcp/products/medical-device",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add huangjunsong404-crypto-china-medical-device-look --url 'https://mcp.agentdatacore.com/mcp/products/medical-device' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  huangjunsong404-crypto-china-medical-device-look:
    url: "https://mcp.agentdatacore.com/mcp/products/medical-device"
```

### Netclaw

```json
{
  "McpServers": {
    "huangjunsong404-crypto-china-medical-device-look": {
      "Transport": "http",
      "Url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
    }
  }
}
```

### Vellum

```bash
assistant mcp add huangjunsong404-crypto-china-medical-device-look -t streamable-http -u 'https://mcp.agentdatacore.com/mcp/products/medical-device'
```

### Other

```json
{
  "mcpServers": {
    "huangjunsong404-crypto-china-medical-device-look": {
      "type": "http",
      "url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, +1)

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

### 2026-09-25 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 69, +1)

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

### 2026-09-21 (score 68, +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-09-19 (score 67, +1)

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

### 2026-09-17 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 65)

First indexed and scored.

## MCP tools (6)

### `get_udi_device` (~237 tokens)

Look up medical-device records when a UDI identifier is known. Inputs: udi. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: udi. Missing required or invalid input produces an argument error.

Input parameters:

- `limit` (integer): Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
- `offset` (integer): Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
- `snapshot` (string): Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…
- `udi` (string, required): Recorded UDI identifier; retain leading zeros. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Required.

### `search_udi_products` (~237 tokens)

Find medical devices by product or trade-name text. Inputs: query. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: query. Missing required or invalid input produces an argument error.

Input parameters:

- `limit` (integer): Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
- `offset` (integer): Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
- `query` (string, required): Recorded product or trade-name text. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not accepted. Required.
- `snapshot` (string): Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

### `get_udi_company_products` (~246 tokens)

Find recorded medical-device products associated with a company or registrant name. Inputs: company. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: company. Missing required or invalid input produces an argument error.

Input parameters:

- `company` (string, required): Recorded registrant/company name, including recorded English names. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not acce…
- `limit` (integer): Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
- `offset` (integer): Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
- `snapshot` (string): Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

### `get_udi_registration_products` (~239 tokens)

Find medical-device records associated with a registration or filing number. Inputs: registration_no. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: registration_no. Missing required or invalid input produces an argument error.

Input parameters:

- `limit` (integer): Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
- `offset` (integer): Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
- `registration_no` (string, required): Recorded registration or filing number, including its original punctuation. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Required.
- `snapshot` (string): Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

### `search_udi_category` (~240 tokens)

Find medical devices by a recorded category name or classification code. Inputs: category. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: category. Missing required or invalid input produces an argument error.

Input parameters:

- `category` (string, required): Recorded device category name or classification code. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not accepted. Required.
- `limit` (integer): Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
- `offset` (integer): Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
- `snapshot` (string): Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

### `get_information_standard` (~42 tokens)

Retrieve definitions of information formation classes, provenance fields and snapshot/version metadata. Takes no arguments. Returns the information-standard document, not business records or an assessment of facts.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 70
- 2026-09-25: 70
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65

## Common questions

### What is the China Medical Device Lookup MCP server?

China Medical Device Lookup is an MCP server listed in the public MCP registry as io.github.huangjunsong404-crypto/china-medical-device-lookup. Look up medical devices in China by UDI, product name, registrant, registration number or category. This page covers its hosted endpoint (https://mcp.agentdatacore.com/mcp/products/medical-device).

### Is the China Medical Device Lookup MCP server safe to use?

China Medical Device Lookup scores 71 out of 100 on VerifyMCP. 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 Medical Device Lookup MCP server expose?

China Medical Device Lookup exposes 6 tools: get_udi_device, search_udi_products, get_udi_company_products, get_udi_registration_products, search_udi_category, get_information_standard. Their descriptions and schemas cost roughly 1,241 tokens of context every time the server is loaded.

### Does the China Medical Device Lookup MCP server require authentication?

No. We connected to China Medical Device Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the China Medical Device Lookup MCP server still maintained?

China Medical Device Lookup is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.agentdatacore.com/mcp/products/medical-device
- Website: https://agentdatacore.com/
- Changelog RSS feed: https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device.xml
- Changelog JSON feed: https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device.json
- HTML version of this page: https://verifymcp.io/servers/huangjunsong404-crypto-china-medical-device-lookup/mcp-products-medical-device