Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MedXpert 标准检索连接器

PYPI · MEDXPERT-STANDARDS-CONNECTOR

Read-only local MCP index of medical-device standards (ISO/GB/YY/ASTM/IEC) with official links.

55 Trust /100

Last scanned (11 hours ago)

Scores higher than 52% of PyPI servers

Category Health and Science

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 348 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • 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.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

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 →

Changelog

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.

  • 20 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 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 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 15 Nov 26 67

    First indexed and scored.

Diagnostics

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-standards-connector@1.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 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 →

MCP tools · 4 exposed · ~259 tokens

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 →

Tool Tokens
get_standard ~52

按 std_key 取某一标准主题文件的完整整理内容(含全部小节与官方链接)。先调用 list_standards 查看可用 std_key。

NameTypeReqDescription
std_keystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_standards ~36

列出标准索引库全部主题文件(枢纽)及覆盖的标准族,返回 JSON 数组。

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

search_standards ~103

在标准索引库中检索关键词(支持中文/英文/标准号,如 'ISO 13485'、'无菌屏障'、 '生物相容性'、'ASTM F138'、'UDI')。返回命中的主题、小节、摘要片段、官方链接与相关度得分。

NameTypeReqDescription
querystringyes–
top_kinteger––
topic_filterstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

standards_by_region ~68

按适用区域筛选标准:输入区域简称(如 '中国' / '国际' / '美国' / '欧盟' / '日本' / 'ISO' / 'ASTM'),返回相关主题文件与官方链接。

NameTypeReqDescription
regionstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the MedXpert 标准检索连接器 MCP server?

MedXpert 标准检索连接器 runs locally as a PyPI package, launched with uvx medxpert-standards-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-standards-connector

# add to Claude Code
claude mcp add zhaoxinghua09-cell-medxpert-standards-connector -- uvx medxpert-standards-connector
Common questions

What is the MedXpert 标准检索连接器 MCP server?

MedXpert 标准检索连接器 is an MCP server listed in the public MCP registry as io.github.zhaoxinghua09-cell/medxpert-standards-connector. Read-only local MCP index of medical-device standards (ISO/GB/YY/ASTM/IEC) with official links. This page covers its PyPI package (medxpert-standards-connector).

Is the MedXpert 标准检索连接器 MCP server safe to use?

MedXpert 标准检索连接器 scores 55 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 标准检索连接器 MCP server expose?

MedXpert 标准检索连接器 exposes 4 tools: list_standards, search_standards, get_standard, standards_by_region. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.

Is the MedXpert 标准检索连接器 MCP server still maintained?

MedXpert 标准检索连接器 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 标准检索连接器 MCP server under?

MedXpert 标准检索连接器 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 标准检索连接器 MCP server?

VerifyMCP ran 15 checks on MedXpert 标准检索连接器, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about MedXpert 标准检索连接器: Malware scan. 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.