China Medical Device Lookup
REMOTE · MCP.AGENTDATACORE.COM · SCANNED SEP 28
Look up medical devices in China by UDI, product name, registrant, registration number or category.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.agentdatacore.com
claude mcp add --transport http huangjunsong404-crypto-china-medical-device-look 'https://mcp.agentdatacore.com/mcp/products/medical-device'
{
"mcpServers": {
"huangjunsong404-crypto-china-medical-device-look": {
"url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
}
}
} {
"servers": {
"huangjunsong404-crypto-china-medical-device-look": {
"type": "http",
"url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
}
}
} [mcp_servers.huangjunsong404-crypto-china-medical-device-look] url = "https://mcp.agentdatacore.com/mcp/products/medical-device"
{
"$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 mcp add huangjunsong404-crypto-china-medical-device-look --url 'https://mcp.agentdatacore.com/mcp/products/medical-device' --transport streamable-http
mcp_servers:
huangjunsong404-crypto-china-medical-device-look:
url: "https://mcp.agentdatacore.com/mcp/products/medical-device" {
"McpServers": {
"huangjunsong404-crypto-china-medical-device-look": {
"Transport": "http",
"Url": "https://mcp.agentdatacore.com/mcp/products/medical-device"
}
}
} assistant mcp add huangjunsong404-crypto-china-medical-device-look -t streamable-http -u 'https://mcp.agentdatacore.com/mcp/products/medical-device'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.agentdatacore.com/mcp/products/medical-device
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.agentdatacore.com | CN=YE1,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a7ec5bb97d88b547abb4eb30a6c23bff4a |
| SANs: agentdatacore.com, api.agentdatacore.com, mcp.agentdatacore.com, www.agentdatacore.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.agentdatacore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agentdatacore.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentdatacore.com/mcp/products/medical-device | Verified | 200 | |
| http (plaintext) | http://mcp.agentdatacore.com/mcp/products/medical-device | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_information_standard ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_udi_company_products ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | 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… |
No output schema declared.
No examples provided.
get_udi_device ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Recorded UDI identifier; retain leading zeros. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Required. |
No output schema declared.
No examples provided.
get_udi_registration_products ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
search_udi_category ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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… |
No output schema declared.
No examples provided.
search_udi_products ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
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.