MCP servers › io.github.MyMedi-AI › mcp-server

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.MyMedi-AI/mcp-server

DME billing and medical coding: code lookup, DMEPOS fee schedules, Medicare prior-auth checks — the publisher's description

8 of 9 record checks metRead-only · tools listed 2026-10-23version 1.7.8JavaScriptMITstandard input/output, streamable HTTP32 tools

Summary

io.github.MyMedi-AI/mcp-server is a remote and local MCP server listed in the official MCP registry at version 1.7.8. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 32 tools, 3 resources and 5 prompts.

Record checks

8 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#10,087 of 15,112 packages by monthly downloads, tied with 39 others
Not ranked by stars: 3 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 32
Described as changing data: 1 of 32 toolsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

1 tool is described as changing something (buy_credits): our AI model's reading of the descriptions, not something we tested. We did not call it.
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.7.8, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-13 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-10-13 to 2026-10-21; 3 in the 90 days before the 2026-10-23 snapshot.

Most recent 3 versions

1.7.8 · 2026-10-21
1.7.7 · 2026-10-20
1.7.6 · 2026-10-13

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.7.8 (published 2026-10-21).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

32tools

3resources

5prompts

1 of 32 tools are described as changing something (creating, editing, deleting, sending or running).

pa_required_checkreads or searches
“Check whether a HCPCS code is on the current CMS Required Prior Authorization List (42 CFR 414.234) on a date of service (default today).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- codestringrequired“HCPCS Level II code (e.g., "E0651")”
- dateOfServicestring“Date of service, YYYY-MM-DD (default today)”
- statestring“2-letter US state or territory; needed for items phased in by state”
denial_code_inforeads or searches
“Explain a DME claim denial code (CARC).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- codestringrequired“CARC denial code (e.g., "CO-50", "PR-1", "197")”
code_lookup_basicreads or searches
“Look up basic metadata for a medical code: code, codeType, description, category, isActive.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- codestringrequired“Medical code to look up (e.g., "M79.3")”
reimbursement_basicreads or searches
“Look up Medicare payment for a code.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- codestringrequired“Medical code (e.g., "97110" or "E1390")”
order_readiness_checklistreads or searches
“Blank pre-delivery checklist for a HCPCS DMEPOS code: the universal standard written order (SWO) elements (42 CFR 410.38(d)), whether the code is on the current CMS Required Face-to-Face Encounter & …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- codestringrequired“HCPCS Level II code (e.g., "E0466")”
- dateOfServicestring“Date of service, YYYY-MM-DD (default today)”
- statestring“2-letter US state or territory; needed for items phased in by state”
modifier_advisorreads or searches
“Editorial guidance on DMEPOS billing modifiers: the KX/GA/GY/GZ medical-necessity and liability family, RR/NU/UE rental-vs-purchase, capped-rental month markers (KH/KI/KJ), and RT/LT laterality.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- codestring“HCPCS DMEPOS code to scope guidance to (e.g., "E0601")”
- categorystring“DMEPOS category instead of a code (e.g., "oxygen", "capped-rental", "prosthetics")”
- scenariostring“Optional situation phrase (e.g., "ABN on file", "bilateral AFO", "converting rental to purchase")”
code_lookupreads or searches
“Look up a medical code (ICD-10, CPT, HCPCS).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
- codestringrequired“Medical code to look up (e.g., "M79.3", "99213", "E0601")”
- codeTypestring“Code system (auto-detected if omitted)”
- statestring“2-letter US jurisdiction (50 states + DC/PR/VI).”
code_lookup_batchreads or searches
“Look up a list of medical codes (ICD-10, CPT, HCPCS) in one call.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
- codesarrayrequired“Medical codes to look up, e.g.”
- codeTypestring“Code system applied to every code (auto-detected if omitted)”
- statestring“2-letter US jurisdiction (50 states + DC/PR/VI).”
code_suggestreads or searches
“Suggest ICD-10-CM, CPT and HCPCS Level II codes from a clinical or equipment description — a term search over the 90K-code CMS database, no language model.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
- descriptionstringrequired“Clinical description to find codes for (e.g., "chronic lower back pain")”
- codeTypestring“Limit to specific code system”
- limitnumber“Max suggestions to return (default 10, max 50)”
code_validatereads or searches
“Check that an ICD-10-CM, CPT or HCPCS Level II code exists and is valid on a date of service: termination and effective dates are applied, so a code deleted after that date still validates.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
5 inputs, 1 required
- codestringrequired“Medical code to validate”
- codeTypestring
- dateOfServicestring“Date of service, YYYY-MM-DD (default today)”
- date_of_servicestring“Same as dateOfService (snake_case spelling)”
- contextobject
code_validate_batchreads or searches
“Validate up to 25 medical codes in one call, each judged as code_validate judges one: exists, and is valid on the date of service (dateOfService, YYYY-MM-DD, applied to every code; default today).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
5 inputs, 1 required
- codesarrayrequired“Medical codes to validate (1-25 per call)”
- codeTypestring“Code system applied to every code”
- dateOfServicestring“Date of service, YYYY-MM-DD, applied to every code (default today)”
- date_of_servicestring“Same as dateOfService (snake_case spelling)”
- contextobject
pa_predictreads or searches
“Prior-authorization outlook for a procedure code.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- procedureCodestringrequired“CPT/HCPCS procedure code (e.g., "E0651", "K0800")”
- payerIdstring“Payer category, e.g.”

Show 20 more tools

pa_statusreads or searches
“Check the status of a prior authorization request tracked in your MyMedi-AI web workspace (by its MyMedi-AI PA id).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs
- authorizationIdstring“Prior authorization ID”
- trackingNumberstring“Tracking number (alternative to authorizationId)”
pa_exposure_reportreads or searches
“Map a supplier HCPCS catalog against the current CMS Required Prior Authorization List and Required Face-to-Face Encounter & Written Order Prior to Delivery List on a date of service (default today).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
- codesarrayrequired“Supplier catalog HCPCS codes, e.g.”
- dateOfServicestring“Date of service, YYYY-MM-DD (default today)”
- statestring“2-letter US state or territory; needed for items phased in by state”
ner_extractreads or searches
“Extract the medical codes already present in de-identified text and check each against the MyMedi-AI code database: ICD-10-CM codes whole, dotted or undotted, with their 7th-character extensions (S72…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- textstringrequired“Clinical text to extract entities from”
- entityTypesarray“Return only these entity types: ICD10_CODE, HCPCS_CODE, CPT_CODE, DATE, MEDICATION_INDICATOR (any letter case; default all).”
claims_validatereads or searches
“Pre-submission check of a claim's codes and dates — no patient or provider identifiers needed or accepted.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
- claimobjectrequired“Claim data to validate”
compliance_auditreads or searches
“Audit one DMEPOS order's documentation against the Original Medicare requirements that apply to its HCPCS code on the date of service: the standard written order (SWO) elements (42 CFR 410.38(d)(1)(i…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- dataobjectrequired“The order: its HCPCS code, date of service and state, and true/false facts about its documentation”
- auditTypestring“Optional: "dme_order", the only audit (the default)”
drug_lookupreads or searches
“Look up drug information including label data, adverse events, and related diagnosis codes.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- drugNamestringrequired“Drug name (brand, generic, or substance — min 2 chars)”
- searchFieldstring“Search field (default: brand_name)”
drug_interactionsreads or searches
“Adverse event reports that name drugs together: coReportCount, the number of FAERS reports naming every listed drug; the reactions most often named in them; and for each reaction a proportional repor…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- drugsarrayrequired“Array of 2-5 different drug names (brand or generic), each matched against the product name reported in FAERS.”
code_reimbursementreads or searches
“Look up Medicare reimbursement rates for a medical code.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
2 inputs, 1 required
- codestringrequired“Medical code (e.g., "99213", "M79.3")”
- codeTypestring“Code system (auto-detected if omitted)”
fee_schedule_lookupreads or searches
“Look up the CMS DMEPOS fee schedule for a DME/orthotic/prosthetic HCPCS code: rental (RR) vs purchase (NU new / UE used), non-rural vs rural, per state.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
3 inputs, 1 required
- codestringrequired“DMEPOS HCPCS code (e.g., "E0601", "K0800", "E1390")”
- statestring“2-letter US jurisdiction (50 states + DC/PR/VI) for exact non-rural/rural rates; omit for national ranges”
- modifierstring“Narrow to rental (RR) or purchase (NU new / UE used)”
trials_searchon 1 other serverreads or searches
“Search active clinical trials by condition, ICD-10 code, or intervention.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
5 inputs
- conditionstring“Medical condition to search for”
- codestring“ICD-10 code (auto-mapped to condition)”
- interventionstring“Drug or intervention name”
- statusstring“Trial status filter (default: RECRUITING)”
- limitnumber“Max results (default 10, max 50)”
code_crossrefreads or searches
“Related codes for an ICD-10-CM, CPT or HCPCS Level II code, across the three code systems.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
1 input, 1 required
- codestringrequired“Medical code to cross-reference (e.g., "M79.3", "99213", "E0601")”
drug_rxnormreads or searches
“Normalize a drug name with NIH RxNorm: returns the matching RxNorm concepts (RxCUI, name, synonym, term type) and the primary RxCUI.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- drugNamestringrequired“Drug name to look up (min 2 chars)”
provider_paymentsreads or searches
“Look up pharmaceutical and device company payments to a physician (Sunshine Act data).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- npistringrequired“10-digit NPI number of the physician”
disease_surveillancereads or searches
“Look up disease surveillance data including case counts and trends by condition and geography.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs
- conditionstring“Disease or condition name (e.g., "Hepatitis A", "Salmonellosis")”
- codestring“ICD-10 code (auto-mapped to condition name)”
- statestring“2-letter state code to filter by geography”
provider_searchreads or searches
“Search the NPI provider directory.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
7 inputs
- firstNamestring
- lastNamestring
- organizationNamestring
- taxonomystring“Provider taxonomy/specialty code”
- citystring
- statestring“2-letter state code”
- limitnumber“Max results (default 10, max 50)”
provider_enrichreads or searches
“Look up a provider by NPI in the CMS NPPES registry (name, credential, primary and other taxonomies, practice address, enumeration date) and add an LLM-generated estimate, labelled as such, of specia…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- npistringrequired“10-digit NPI number”
drug_enrichreads or searches
“Look up a drug by brand or generic name in openFDA and return its first matching FDA label: brand and generic name, manufacturer, NDCs, route, substance, product type, and the label's indications, wa…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- drugNamestringrequired“Drug name (brand or generic, min 2 chars)”
- searchFieldstring“Match the name against the label's brand name or generic name (default: brand_name)”
market_analysisreads or searches
“Specialty snapshot for a US state: how many providers one CMS NPPES registry query matches for the specialty (the query returns at most 200 records, so the figure is a floor, not a provider count), p…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- statestringrequired“2-letter state code (e.g., "TX", "CA")”
- specialtystringrequired“Medical specialty (e.g., "cardiology", "orthopedics")”
account_statuson 22 other serversreads or searches
“Check your MyMedi-AI account: current credit balance, USD equivalent, transaction count, recent transactions, and last activity.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
buy_creditson 20 other serversmoves moneydescribed as changing data
“Top up your MyMedi-AI credits.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
- amountnumber“USD amount to purchase (min $1 = 1,000 credits)”
- packagestring“Named package: starter $1/1k, basic $5/5k, standard $25/25k, professional $100/100k, enterprise $500/500k credits (alternative to amount)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 32 tools
Says what it returns: 100% of 32 tools
States limits, defaults or errors: 100% of 4 tools
Says when to use it: 100% of 32 tools
Items covered per tool: 4.0 of 4 on average

Counted from the listing

Parameters with a description: 91% of 76
Tools with a description: 100% of 32
Typical description length: 479 characters

The tool set

Counted from the listing

Tools: 32
Size of the list: about 10,399 tokens for an agent to load (characters ÷ 4)
Naming: 32 of 32 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 32 of 32 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @mymedi-ai/mcp-server

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mymedi-ai/mcp-server@1.7.8"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mymedi-ai/mcp-server@1.7.8"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mymedi-ai/mcp-server@1.7.8"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@mymedi-ai/mcp-server@1.7.8"]}'

Claude Code

claude mcp add --transport stdio mcp-server -- npx -y @mymedi-ai/mcp-server@1.7.8

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @mymedi-ai/mcp-server@1.7.8

Optional settings the entry also lists (left out above): MCP_API_KEY.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mymedi-ai.com/mcp-stream

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mymedi-ai.com/mcp-stream"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "mcp-server": {
      "type": "http",
      "url": "https://mymedi-ai.com/mcp-stream"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"mcp-server","type":"http","url":"https://mymedi-ai.com/mcp-stream"}'

Claude Code

claude mcp add --transport http mcp-server https://mymedi-ai.com/mcp-stream

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mymedi-ai.com/mcp-stream --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 1.7.8
Latest stable: 1.7.8
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-beDLIexyJWAIBP3xz…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 191 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mymedi-ai.com/mcp-stream	Endpoint answered and asked for sign-in	matches	our test · 2026-10-23
No credential declared as required	Required sign-in	differs	our test · 2026-10-23
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 1.7.8 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/MyMedi-AI/mymedi-ai-mcp-server	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.MyMedi-AI
GitHub owner: an organization (MyMedi-AI)
Build record: signed and attested

Repository: github.com/MyMedi-AI/mymedi-ai-mcp-server
Stars: 3
Repository age: 181–365 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 9 record checks met

#10,087 of 15,112 packages by monthly downloads, tied with 39 others
Not ranked by stars: 3 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.MyMedi-AI/mcp-server

Answered from the data above

Is io.github.MyMedi-AI/mcp-server safe to install?

We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.MyMedi-AI/mcp-server been security tested?

Partly. 3 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.MyMedi-AI/mcp-server do?

It lists 32 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and move money. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.MyMedi-AI/mcp-server change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.MyMedi-AI/mcp-server publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 1.7.8, the latest stable release on npm.

Where is the source code of io.github.MyMedi-AI/mcp-server?

In github.com/MyMedi-AI/mymedi-ai-mcp-server, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

3 exercised10 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a remote test (1 of 18 applicable checks exercised).

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
4,930 msConnected after 0 redirects.
Read the inventory: 32 tools, 3 resources, 5 prompts.
6,403 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

not known (our limit)

The website shows almost no text without JavaScript, and we did not re-read it in a browser. This is our limit.

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

remote and local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output, streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

191 downloads a month

package registry · 2026-10-23

Publisher signals

owner: an organization · repository age: 181–365 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

either (remote or your machine)

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.MyMedi-AI/mcp-server: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.MyMedi-AI/mcp-server

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.MyMedi-AI/mcp-server)](https://protocolprobe.com/mcp/servers/io.github.MyMedi-AI/mcp-server)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology