Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
MedXpert Orthopedic Instrument Testing and Integration is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Orthopedic device testing MCP: lab match, quotes, UDI, standards, timelines, gap reports. Offline.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user medxpert-orthopedic-instrument-testing-and-in-mcp '--' uvx medxpert-ortho-mcp
# 2 — ask your agent for something these tools do
# match_labs, calc_quote, check_udi and 5 more
MedXpert Orthopedic Instrument Testing and Integration costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts MedXpert Orthopedic Instrument Testing and Integration as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user medxpert-orthopedic-instrument-testing-and-in-mcp '--' uvx medxpert-ortho-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take ORTHO_DATA_DIR (Directory of your own JSON datasets (labs/quotes/udi/standards/judgment_trees/timelines). Omit to use the bundled sample data.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
按能力关键词 / 地区 / 器械描述给检测机构打分排序。例:scope_keyword='力学疲劳'。返回命中能力项与联系方式;示例数据仅 3 家机构。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_keyword | string | no | 能力关键词,如 力学疲劳、生物相容性 |
| region | string | no | 地区码,如 CN-JS |
| device | string | no | 器械描述,如 接骨板 |
| limit | number | no | 返回条数,默认 5 |
按机构与能力项取报价区间并按数量估算总额(含超出含样量加价规则)。价格是示例区间,不构成商务承诺。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lab_id | string | yes | 机构 ID,来自 match_labs |
| scope | string | yes | 能力项,如 力学疲劳 |
| quantity | number | no | 样品数量,默认 1 |
校验 14 位 UDI-DI 并回出分类/无菌/一次性属性。未命中会说明示例数据范围,不代表真实数据库无此编号。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| udi_di | string | yes | 14 位 UDI-DI |
按关键词查标准,并可带 as_of 做双时态判定:该日是否已生效、是否已被替代。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 标准号或题名关键词 |
| as_of | string | no | 判定基准日 YYYY-MM-DD(可选) |
取分类/路径判定树(逐步问答结构)。演示结构,最终以分类目录与界定结论为准。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| procedure | string | no | 程序名,如 骨科植入物注册 |
| region | string | no | 地区码,默认 CN |
取地区路径:受理机关、路径说明与该程序的必备材料清单。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | 地区码,如 CN、CN-JS |
| procedure | string | no | 程序名(可选) |
把相对天数展开成日历日期,并按 as_of 标出 completed/in_progress/not_started 与逾期未启动项。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| procedure | string | no | 程序名,默认 骨科植入物注册 |
| region | string | no | 地区码,默认 CN |
| start_date | string | no | 起始日 YYYY-MM-DD(默认今天) |
| as_of | string | no | 判定基准日 YYYY-MM-DD(默认今天) |
对照必备材料清单报缺口:给已具备材料名列表,返回缺失项与完整度。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| present | array | yes | 已具备的材料名列表 |
| procedure | string | no | 程序名,默认 骨科植入物注册 |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MedXpert Orthopedic Instrument Testing and Integration or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish MedXpert Orthopedic Instrument Testing and Integration can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.