MedXpert Regulatory Hub
PYPI · MEDXPERT-REG-HUB
Read-only medical device regulatory data: NMPA UDI, FDA 510(k)/PMA/classification lookups.
Available components
Last scanned (2 hours ago)
Scores higher than 68% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 457 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 52
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 5 Nov 2026 · Analysed pypi/medxpert-reg-hub@2.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
class_lookup ~63
FDA 医疗器械产品分类查询（21 CFR 分类 7,088 条）：按 产品代码（如 HRX）或 产品名称/device_name。返回最多 10 条。
| Name | Type | Req | Description |
|---|---|---|---|
| product_code | string | – | – |
| product_name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fda_510k_lookup ~74
FDA 510(k) 数据库查询：按 K 号精确（如 K234042），或按 公司/applicant、产品名 模糊。返回最多 10 条。
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| k_number | string | – | – |
| product | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
hub_search ~95
医械注册枢纽知识库关键词检索：跨 20 大枢纽（注册工程师资料/UDI/STED/GMP/临床评价/上市后监管/市场准入等）检索产品分类与注册路径要点，返回命中文件、行号与上下文。适合"某产品在X国怎么注册"类问题。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pma_lookup ~67
FDA PMA（上市前批准）查询：按 PMA 号（如 P980016）、公司或产品模糊。返回最多 10 条。
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| pma_number | string | – | – |
| product | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
udi_lookup ~117
NMPA 医疗器械唯一标识（UDI）查询：按 主DI 精确查，或按 产品名称/注册证号 模糊查。返回最多 20 条。 字段：udi_main 主DI、product_name 产品名称、spec 规格、reg_no 注册证号、regrant_name 注册人、class_code 分类编码、device_class 类别、issue_date 发码日期。
| Name | Type | Req | Description |
|---|---|---|---|
| di | string | – | – |
| product_name | string | – | – |
| reg_no | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MedXpert Regulatory Hub MCP server?
MedXpert Regulatory Hub runs locally as a PyPI package, launched with uvx medxpert-reg-hub. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · medxpert-reg-hub
claude mcp add stevenzhao07-medxpert-reg-hub -- uvx medxpert-reg-hub
What is the MedXpert Regulatory Hub MCP server?
MedXpert Regulatory Hub is an MCP server listed in the public MCP registry as io.github.stevenzhao07/medxpert-reg-hub. Read-only medical device regulatory data: NMPA UDI, FDA 510(k)/PMA/classification lookups. This page covers its PyPI package (medxpert-reg-hub).
Is the MedXpert Regulatory Hub MCP server safe to use?
MedXpert Regulatory Hub scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 MedXpert Regulatory Hub MCP server expose?
MedXpert Regulatory Hub exposes 5 tools: udi_lookup, fda_510k_lookup, pma_lookup, class_lookup, hub_search. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.
Is the MedXpert Regulatory Hub MCP server still maintained?
MedXpert Regulatory Hub is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MedXpert Regulatory Hub MCP server under?
MedXpert Regulatory Hub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.