MedXpert Global Regulatory Connector (reg-connector)
PYPI · MEDXPERT-REG-CONNECTOR
Read-only MCP for medical-device regulation (NMPA/FDA/MDR/PMDA): 27 hubs, 7 tools, freshness guard.
Available components
Last scanned (17 hours ago)
Scores higher than 64% 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 15 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 (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 822 tokens (~117/item across 7 items; 7 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 56
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 21 Nov 2026 · Analysed pypi/medxpert-reg-connector@1.3.5
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 | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 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 →
ask_classification Ask Classification ~101
产品分类与注册路径速查:输入产品描述(如 '骨科金属接骨板'、'一次性使用输液器'), 返回相关枢纽、分类线索、官方链接与注册路径建议。
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | 产品描述的自然语言表述,宜含材质/结构/用途,如 "骨科金属接骨板"、"一次性使用输液器"。 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_hub Get Hub ~95
按 hub_key 取某一枢纽的完整整理内容(含全部小节与官方链接、时效与标准指针)。先调用 list_hubs 查看可用 hub_key。
| Name | Type | Req | Description |
|---|---|---|---|
| hub_key | string | yes | 枢纽标识,必须是 list_hubs 返回的 hub_key 之一(如 "风险管理枢纽"、"UDI全球标识枢纽")。 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_freshness Kb Freshness ~68
报告知识库新鲜度:全库统计 + 逐枢纽 as_of/age_days/freshness/next_review, 并列出逾期未复核的枢纽。法规会更新,调用知识前建议先查新鲜度。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kb_sources Kb Sources ~88
列出官方源注册表(sources.json):各源权威机构、巡检通道(api/rss/page/sparql/catalog)、 巡检频率、是否可全自动、版权等级。可选按辖区过滤。
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | 辖区过滤,取 CN / US / EU / JP / GLOBAL;留空则返回全部官方源。 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_hubs List Hubs ~35
列出法规知识库全部枢纽(主题)及覆盖范围、时效状态,返回 JSON 数组。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reg_delta Reg Delta ~127
列出巡检发现的法规变更流水(读 registry.deltas)。可选按起始日期与辖区过滤。 无巡检记录时返回空并提示如何产生。
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | 辖区过滤,取 CN / US / EU / JP / GLOBAL;留空则不按辖区过滤。 |
| limit | integer | – | 返回最近条数上限,默认 50。 |
| since | string | – | 起始日期,格式 YYYY-MM-DD,仅返回该日及之后登记的变更;留空则返回全部。 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_regulation Search Regulation ~199
在法规知识库中检索关键词(支持中文/英文/法规号,如 'UDI'、'510k'、'MDR PMS'、'委托生产')。 返回命中的枢纽、小节、摘要片段、官方链接、相关度得分与时效标注(as_of/freshness)。
| Name | Type | Req | Description |
|---|---|---|---|
| hub_filter | string | – | 可选,仅在该枢纽内检索;取值须为 list_hubs 返回的 hub_key 之一。 |
| query | string | yes | 检索关键词。中英文或法规号均可,如 "UDI"、"510k"、"MDR PMS"、"委托生产"、"ISO 10993"。 |
| top_k | integer | – | 返回条数上限,默认 5;建议 3-10,过大只会稀释上下文而不提升召回精度。 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MedXpert Global Regulatory Connector (reg-connector) MCP server?
MedXpert Global Regulatory Connector (reg-connector) runs locally as a PyPI package, launched with uvx medxpert-reg-connector. 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-connector
claude mcp add zhaoxinghua09-cell-medxpert-reg-connector -- uvx medxpert-reg-connector
What is the MedXpert Global Regulatory Connector (reg-connector) MCP server?
MedXpert Global Regulatory Connector (reg-connector) is an MCP server listed in the public MCP registry as io.github.zhaoxinghua09-cell/medxpert-reg-connector. Read-only MCP for medical-device regulation (NMPA/FDA/MDR/PMDA): 27 hubs, 7 tools, freshness guard. This page covers its PyPI package (medxpert-reg-connector).
Is the MedXpert Global Regulatory Connector (reg-connector) MCP server safe to use?
MedXpert Global Regulatory Connector (reg-connector) scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Global Regulatory Connector (reg-connector) MCP server expose?
MedXpert Global Regulatory Connector (reg-connector) exposes 7 tools: list_hubs, search_regulation, get_hub, ask_classification, kb_freshness, and 2 more. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.
Is the MedXpert Global Regulatory Connector (reg-connector) MCP server still maintained?
MedXpert Global Regulatory Connector (reg-connector) is still listed as active in the MCP registry. We last reached this channel on 21 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 Global Regulatory Connector (reg-connector) MCP server under?
MedXpert Global Regulatory Connector (reg-connector) declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the MedXpert Global Regulatory Connector (reg-connector) MCP server?
VerifyMCP ran 15 checks on MedXpert Global Regulatory Connector (reg-connector), covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about MedXpert Global Regulatory Connector (reg-connector): Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.