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.

io.github.kriskraw80/mychart

NPM · MYCHART-MCP-SERVER · SCANNED AUG 7

Connects to Epic MyChart patient portals: interactive login, list and download your own test results

Available components

65 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1122 tokens (~140/item across 8 items; 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mychart-mcp-server

# add to Claude Code
claude mcp add kriskraw80-mychart -- npx -y mychart-mcp-server
# add to Codex CLI
codex mcp add kriskraw80-mychart -- npx -y mychart-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kriskraw80-mychart": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mychart-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kriskraw80-mychart --command npx --arg -y --arg mychart-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  kriskraw80-mychart:
    command: "npx"
    args: ["-y", "mychart-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "kriskraw80-mychart": {
      "command": "npx",
      "args": [
        "-y",
        "mychart-mcp-server"
      ]
    }
  }
}
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.

  • 4 Aug 26 65

    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 7 Aug 2026 · Analysed npm/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 98 packages
Packages resolved 98
Deprecated 96
Stale 30
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 8 exposed · ~1,122 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.

Tool Tokens
mychart_close_browser ~45

Close the automation browser. The login session itself is preserved in the persistent profile on disk — this only frees the browser process. The next tool call relaunches it automatically.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mychart_download_test_result ~162

Save one test result as a PDF file on disk (rendered from the result detail page). Requires a logged-in session. Args: - result_id (string): An id from mychart_list_test_results (e.g. "r3"), or a full result-detail URL. - filename (string, optional): Base filename for the PDF; defaults to "<date> <test name>.pdf". Files are saved to ~/.mychart-mcp/downloads. Returns: { path, bytes, id, name, date }.

NameTypeReqDescription
filenamestringOptional base filename for the saved PDF
result_idstringyesResult id from mychart_list_test_results (e.g. "r3") or a full result URL

No output schema declared.

No examples provided.

mychart_get_test_result ~135

Open one test result and return its full readable content — component values, reference ranges, flags, and provider comments — as text. Requires a logged-in session. Args: - result_id (string): An id from mychart_list_test_results (e.g. "r3"), or a full result-detail URL. Returns: { id, name, date, url, text, truncated }. If truncated is true, use mychart_download_test_result for the complete PDF.

NameTypeReqDescription
result_idstringyesResult id from mychart_list_test_results (e.g. "r3") or a full result URL

No output schema declared.

No examples provided.

mychart_list_test_results ~231

Fetch the full list of test results from the MyChart portal (labs, imaging, pathology, etc.). Automatically expands lazy-loaded lists ("Show more") so every available result is returned, newest first as displayed by MyChart. Requires a logged-in session. Returns: JSON with schema: { "count": number, "listUrl": string, // the portal page that was scraped "results": [ { "id": string, // stable id for this session, e.g. "r1" — use with mychart_get_test_result / mychart_download_test_result "name": string, // test name, e.g. "CBC WITH DIFFERENTIAL" "date": string?, // collection/result date as shown by MyChart "url": string // direct link to the result detail page } ] } Error Handling: - "Not logged in" -> run mychart_login first. - If no results are recognized, use mychart_screenshot to inspect what the portal is showing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mychart_login ~202

Open a VISIBLE browser window at the configured MyChart login page and wait for the sign-in to complete. The user types their username/password and completes any MFA prompt directly in that window — credentials are never passed through the MCP client. (Optionally, if MYCHART_USERNAME and MYCHART_PASSWORD environment variables are set on the server process, the login form is pre-filled.) Tip: check "Remember this device" during MFA so future logins skip the code. The session is stored in a persistent browser profile (~/.mychart-mcp/browser-profile), so once logged in, all other tools work headlessly without repeating login until the session expires. Args: - timeout_seconds (number): How long to wait for the user to finish signing in (default 300, max 900). Returns: { success, landedUrl, message }

NameTypeReqDescription
timeout_secondsintegerSeconds to wait for the user to complete sign-in (default 300)

No output schema declared.

No examples provided.

mychart_screenshot ~100

Debug aid: capture a full-page PNG of whatever page the automation browser is currently on (or the MyChart home page if idle). Useful when list/detail scraping reports nothing recognizable — the screenshot shows what the portal actually rendered. Args: - name (string, optional): Base filename for the PNG. Returns: { path, url }. Screenshot is saved to ~/.mychart-mcp/downloads.

NameTypeReqDescription
namestringOptional base filename

No output schema declared.

No examples provided.

mychart_session_status ~64

Check whether a MyChart provider is configured and whether the saved browser session is still logged in. Runs headless; safe to call any time. Returns: { configured, baseUrl, loggedIn, landedUrl }. If loggedIn is false, run mychart_login.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mychart_set_provider ~183

Configure which health system's MyChart site to use. Every hospital system runs its own MyChart instance at its own URL, so this must be set once before logging in. Args: - url (string): Any URL from the provider's MyChart site — the login page URL pasted from a browser works fine (e.g. "https://mychart.virtua.org/MyChartPRD/Authentication/Login"). It is normalized to the instance root automatically. Returns: The normalized base URL that was saved. The setting persists in ~/.mychart-mcp/config.json. Changing providers invalidates any saved login session for the previous provider only in the sense that tools will now target the new site.

NameTypeReqDescription
urlstringyesAny URL on your health system's MyChart site, e.g. https://mychart.virtua.org/MyChartPRD

No output schema declared.

No examples provided.