io.github.kriskraw80/mychart
NPM · MYCHART-MCP-SERVER · SCANNED SEP 22
Connects to Epic MyChart patient portals: interactive login, list and download your own test results
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 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 (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.kriskraw80/mychart MCP server?
io.github.kriskraw80/mychart runs locally as an npm package, launched with npx -y mychart-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mychart-mcp-server
claude mcp add kriskraw80-mychart -- npx -y mychart-mcp-server
{
"mcpServers": {
"kriskraw80-mychart": {
"command": "npx",
"args": [
"-y",
"mychart-mcp-server"
]
}
}
} {
"servers": {
"kriskraw80-mychart": {
"command": "npx",
"args": [
"-y",
"mychart-mcp-server"
]
}
}
} codex mcp add kriskraw80-mychart -- npx -y mychart-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kriskraw80-mychart": {
"type": "local",
"command": [
"npx",
"-y",
"mychart-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add kriskraw80-mychart --command npx --arg -y --arg mychart-mcp-server
mcp_servers:
kriskraw80-mychart:
command: "npx"
args: ["-y", "mychart-mcp-server"] {
"McpServers": {
"kriskraw80-mychart": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mychart-mcp-server"
]
}
}
} assistant mcp add kriskraw80-mychart -t stdio -c npx -a -y mychart-mcp-server
{
"mcpServers": {
"kriskraw80-mychart": {
"command": "npx",
"args": [
"-y",
"mychart-mcp-server"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/mychart-mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| 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 →
mychart_close_browser Close MyChart 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 Download MyChart Test Result as PDF ~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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Optional base filename for the saved PDF |
| result_id | string | yes | Result 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 Get MyChart Test Result Details ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| result_id | string | yes | Result 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 List MyChart 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 Log in to MyChart ~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 }
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | integer | – | Seconds to wait for the user to complete sign-in (default 300) |
No output schema declared.
No examples provided.
mychart_screenshot Screenshot Current MyChart Page ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional base filename |
No output schema declared.
No examples provided.
mychart_session_status Check MyChart Session ~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 Set MyChart 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any URL on your health system's MyChart site, e.g. https://mychart.virtua.org/MyChartPRD |
No output schema declared.
No examples provided.
What is the io.github.kriskraw80/mychart MCP server?
io.github.kriskraw80/mychart is an MCP server listed in the public MCP registry as io.github.kriskraw80/mychart. Connects to Epic MyChart patient portals: interactive login, list and download your own test results. This page covers its npm package (mychart-mcp-server).
Is the io.github.kriskraw80/mychart MCP server safe to use?
io.github.kriskraw80/mychart scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.kriskraw80/mychart MCP server expose?
io.github.kriskraw80/mychart exposes 8 tools: mychart_set_provider, mychart_login, mychart_session_status, mychart_list_test_results, mychart_get_test_result, and 3 more. Their descriptions and schemas cost roughly 1,122 tokens of context every time the server is loaded.
Is the io.github.kriskraw80/mychart MCP server still maintained?
io.github.kriskraw80/mychart is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.kriskraw80/mychart MCP server under?
io.github.kriskraw80/mychart declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.