OpenRecord — MyChart for Claude
MCPB · OPENRECORD.MCPB
Read and manage your Epic MyChart records: labs, meds, imaging, notes, messages, refills.
Available components
Last scanned (19 hours ago)
Scores higher than 70% of MCPB servers
Category Health and Science
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency32
- 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
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability44
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13611 tokens (~189/item across 72 items; 71 tools + 1 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 Management27
- Stability observed for 8 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
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 73 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
- Supports UI / widget rendering.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.
Checks we ran (13)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (4)
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 Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
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 →
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 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.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 32
First indexed and scored.
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 mcpb/https://github.com/Fan-Pier-Labs/openrecord/releases/download/mcpb-v2.3.0/openrecord.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
add_emergency_contact Add an emergency contact ~165
Add a new emergency contact to the record.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| name | string | yes | Contact’s full name. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
| phone_number | string | yes | Contact phone number. |
| relationship_type | string | yes | Relationship, e.g. "Spouse", "Parent", "Sibling", "Friend". |
No output schema declared.
No examples provided.
check_pending_call Check a pending tool call ~293
Collect the result of a tool call that ran past 2.5 minutes and was parked under an id, exactly as the original tool would have returned it. A result that is ready is always handed over, and handed over once — including under `wait: false`, so this is a collection, never a peek. When the call is still running it waits up to 2.5 minutes for it, or with `wait: false` says so at once. Omit `id` to list every pending call, which is what a refusal naming an id is talking about. `abandon: true` stops waiting and discards the result — it does not stop the work, and anything already sent still lands, so an abandoned call is still waitable here until its read finishes. Two clocks: a call that has not finished is given up on 10 minutes after it started, releasing everything it held, and a finished result then waits 10 more minutes to be collected.
| Name | Type | Req | Description |
|---|---|---|---|
| abandon | boolean | – | Stop waiting and discard the result. Does not stop the work. |
| id | string | – | The id from the parking note. Omit to list every pending call. |
| wait | boolean | – | Wait up to 2.5 minutes for the call to finish (default true). false reports at once instead — but a result that is already ready is handed over, and consumed, either way. |
No output schema declared.
No examples provided.
complete_2fa Finish 2FA (step 2) ~166
Finish a sign-in that returned `need_2fa` — from setup_account, connect_imported_account, or a data tool that had to sign in. Pass the `pending_id` from that response and the 6-digit code the user gave you. After a data tool's `need_2fa`, call that data tool again once this succeeds. On success the account is saved and immediately usable. Like setup_account it changes no sign-in settings; on `logged_in`, treat `passkey_saved` and `message` exactly as you would from setup_account.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 6-digit code the user read from email/SMS/authenticator. |
| pending_id | string | yes | The pending_id from the response whose state was need_2fa. |
No output schema declared.
No examples provided.
connect_google_calendar Sync appointments to Google Calendar ~122
Sync the user's upcoming MyChart appointments (every connected account) to their Google Calendar, and keep them in sync every 4 hours. macOS only. Only call this when the user has asked for it. Call it first without confirmed_with_user: that changes nothing and returns what setup involves, to explain to the user. Call it again with confirmed_with_user: true only after the user has agreed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed_with_user | boolean | – | true only once the user has read what setup involves (returned by a call without this) and agreed to go ahead. |
No output schema declared.
No examples provided.
connect_imported_account Connect an account found in the browser ~136
Log into a MyChart account discovered by import_browser_passwords, using the password already saved in the browser, and save it for future calls. Only call this for an entry the user explicitly chose. When several browsers saved different passwords for the login, each is tried until one is accepted. Same outcomes as setup_account: `logged_in`, `need_2fa` (call complete_2fa next), or `invalid_login` (every saved password is stale — ask the user for the current one and use setup_account).
| Name | Type | Req | Description |
|---|---|---|---|
| import_id | string | yes | The import_id of the chosen entry from import_browser_passwords. |
No output schema declared.
No examples provided.
delete_message Delete a conversation ~128
Delete a message conversation from the inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| conversation_id | string | yes | Conversation id from get_messages. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
delete_passkey Delete passkeys ~92
Delete a passkey from the MyChart account by rawId, or every registered passkey when no id is given.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| raw_id | string | – | rawId from list_passkeys. Omit to delete every passkey on the account. |
No output schema declared.
No examples provided.
disable_totp Turn off the authenticator app ~61
Turn off authenticator-app (TOTP) two-factor authentication on this MyChart account.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
No output schema declared.
No examples provided.
disconnect_account Forget a MyChart account ~58
Forget a saved MyChart account. Deletes the local credentials, passkey, and cached session for this login only — other usernames saved for the same hostname are untouched.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account id from list_accounts (`username@hostname`). |
No output schema declared.
No examples provided.
disconnect_google_calendar Turn off Google Calendar sync ~107
Turn off Google Calendar sync: revokes OpenRecord's access to the user's Google account, quits the menu-bar app and stops it starting at login. The app itself stays on disk at ~/.openrecord-mcpb/bin/openrecord-calendar (about 100 MB) so turning sync back on needs no download. The "MyChart Appointments" calendar and its events stay in Google Calendar, and connecting again later reuses that calendar. Only call this when the user has asked for it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
download_billing_statement Download billing statement ~310
Download one billing statement or itemized bill as the PDF MyChart serves for it. Identify it with the `RecordID` of a statement from get_billing. The file is saved on the user’s own device and the path returned.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
| record_id | string | yes | The `RecordID` of the chosen statement from get_billing. Copy it verbatim. |
| return_content | boolean | – | Also put the file's content in the result so it can be read here: a text file as text (a picture is shown whenever it fits, with or without this). Defaults to false — the file is only saved to the us… |
No output schema declared.
No examples provided.
download_document Download document ~326
Download one Document Center document as the file MyChart serves for it — a PDF, an image (TIF/JPG/PNG) or an e-signed HTML document. Identify it with the `dcsID` of a document from get_documents. The file is saved on the user’s own device and the path returned.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| document_id | string | yes | The `dcsID` of the chosen document from get_documents. Copy it verbatim. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
| return_content | boolean | – | Also put the file's content in the result so it can be read here: a text file as text (a picture is shown whenever it fits, with or without this). Defaults to false — the file is only saved to the us… |
No output schema declared.
No examples provided.
download_imaging_study Download imaging study ~315
Download every picture in one imaging study. Identify the study with the `image_id` from get_imaging_results (or its 0-based `imaging_index`). Images are downloaded and decoded on the user’s own device.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| image_id | string | – | The `image_id` from the chosen get_imaging_results entry. Copy it verbatim. |
| imaging_index | number | – | Alternative to image_id: the 0-based index of the study in get_imaging_results. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
| save_to_downloads | boolean | – | Save the pictures to the user's Downloads folder, as full-resolution JPEGs in a folder named for the study, INSTEAD of showing them in the conversation. Defaults to false — reduced-size previews are… |
| study_name | string | – | Human-readable study name used to label the output. Optional. |
No output schema declared.
No examples provided.
get_activity_feed Activity feed ~171
Recent account activity feed items.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_allergies Allergies ~173
Known allergies with reaction and severity.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_billing Billing ~171
Billing history and account balances.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_care_journeys Care journeys ~174
Care journeys and care plans.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_care_team Care team ~186
Providers on the care team, including outside providers, each with their role, specialty and NPI.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_documents Documents ~170
Clinical documents and visit records.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_education_materials Education materials ~176
Patient education materials assigned by the care team.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_ehi_export EHI export templates ~175
Electronic Health Information export templates this instance offers.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_emergency_contacts Emergency contacts ~171
Emergency contacts on file.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_goals Goals ~173
Care team goals and patient-set goals.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_health_issues Health issues ~173
Active health issues / problem list.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_health_summary Health summary ~183
Health summary — vitals snapshot, blood type, smoking status and similar top-level facts.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_hospital_info Public profile of a health system ~271
What a MyChart instance publishes about its health system to anyone, with no account: the organization's support, scheduling and billing phone lines and support email; the "Find a Doctor" directory of bookable providers (name, credentials, specialties, languages, photo) with every clinic they work at (street address, phone, coordinates, hours); billing entities and their facilities; and which portal features are switched on. Pass the `hostname` from search_mycharts. Slow on large systems — one specialty is 0.6–2 MB and some list twenty — so narrow with `specialties` or skip the crawl with `include_providers: false`. Never returns a fax number or an accepted-insurance list: MyChart publishes neither (the payer list sits behind a reCAPTCHA-protected disclaimer).
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | The MyChart hostname, e.g. mychart.example.org. A full login URL also works. |
| include_billing | boolean | – | Read the billing entities (default true). |
| include_providers | boolean | – | Crawl the provider and clinic directory (default true). |
| max_specialties | integer | – | Stop after this many specialties. |
| specialties | array | – | Only crawl these "Find a Doctor" specialties (by name). Default: all of them. |
No output schema declared.
No examples provided.
get_imaging_results Imaging results ~211
Imaging result metadata (X-ray, MRI, CT, ultrasound, …) with reports. Entries that have viewable pictures carry an `image_id` — pass that to download_imaging_study to get the actual images.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_immunizations Immunizations ~170
Vaccination history.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_insurance Insurance ~201
Insurance coverages on file: payer, plan, member and group numbers, effective dates. Not the deductible or out-of-pocket maximum — those are get_insurance_benefits.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_insurance_benefits Insurance benefits ~239
How much of the deductible and the out-of-pocket maximum has been used, how much is left, and when each resets. MyChart keys these to a billing guarantor account rather than to a coverage, so a patient with two accounts gets one set per account. For the coverages themselves — payer, plan, member id — use get_insurance.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_insurance_payers Insurance payers accepted ~215
The insurance payers this organization's MyChart offers when adding a coverage — the organization's configured payer catalogue, the same for every patient on the instance. Not the patient's own coverage (that is get_insurance) and not an in-network guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_lab_results Lab results ~176
Lab results with reference ranges and prior values for trending.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_letter_details Letter contents ~210
The full contents of one letter listed by get_letters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| csn | string | yes | csn from the chosen get_letters entry. |
| hno_id | string | yes | hnoId from the chosen get_letters entry. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_letters Letters ~183
Letters from providers. Each entry carries the hnoId/csn needed by get_letter_details.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_linked_accounts Linked MyChart accounts ~179
MyChart accounts at other organizations that are linked to this one.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_medical_history Medical history ~176
Past medical, surgical, family and social history.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_medications Medications ~177
Current medications with dosage, instructions, prescriber and pharmacy.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_message_attachment Message attachment ~336
Download one file attached to a message — a PDF, photo or other document a provider or the patient attached. Identify it by the conversation_id from get_messages and the attachment_id (the attachment’s dcsId) from get_message_thread. The file is saved on the user’s own device; images are also shown inline.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| attachment_id | string | yes | The attachment’s dcsId from get_message_thread. Copy it verbatim. |
| conversation_id | string | yes | Conversation id from get_messages. |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
| return_content | boolean | – | Also put the file's content in the result so it can be read here: a text file as text (a picture is shown whenever it fits, with or without this). Defaults to false — the file is only saved to the us… |
No output schema declared.
No examples provided.
get_message_recipients Message recipients ~177
Providers and departments that can receive a new message.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_message_thread Message thread ~219
Every message in one conversation: text, date, sender, and for each attachment its name and dcsId. An attachment's content is a separate call — get_message_attachment with that dcsId.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| conversation_id | string | yes | Conversation id from get_messages. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_message_topics Message topics ~175
Topics/categories a new message can be filed under.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_messages Messages ~206
Every conversation in the inbox: its id, subject, who it is with, when the latest message arrived, and whether it is unread, urgent or has attachments. The messages themselves come from get_message_thread.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_note_content Note content ~245
Fetch the rendered content of a single clinical note listed by get_visit_notes.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| csn | string | yes | Visit CSN from get_past_visits. |
| hno_dat | string | yes | hnoDAT of the chosen note. |
| hno_id | string | yes | hnoID of the chosen note. |
| lrp_id | string | yes | lrpID from get_visit_notes. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_past_visits Past visits ~194
Every past visit MyChart holds, newest first. `hasOlderVisits` says whether the page cap stopped the walk before the end.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_preventive_care Preventive care ~178
Preventive care recommendations — overdue and upcoming screenings.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_profile Patient profile ~187
Patient profile (name, date of birth, medical record number, primary care provider) plus the account email address.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_questionnaires Questionnaires ~173
Open and completed questionnaires / health assessments.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_referrals Referrals ~170
Active and past referrals.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
get_setup_widget Get interactive setup widget ~71
Display an interactive widget for connecting MyChart accounts: the user can import logins already saved in their browser, or search for their health system and sign in by hand, then finish 2FA and the passkey offer in the widget. Use this if the user wants a GUI instead of chat-based setup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_upcoming_orders Upcoming orders ~182
Standing/upcoming orders — labs, imaging and procedures the care team has ordered.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Which connected MyChart account to use, as `username@hostname`. Get the exact value from the `account` field of list_accounts. |
| mode | string | – | Output mode: `concise` (markdown, the interesting fields), `standard` (markdown, every useful field), `json` (the standard fields as JSON), or `raw` (the untouched MyChart response, large). Default:… |
| patient | string | – | Which patient's record this call is about, for accounts with MyChart proxy access to family members' charts — a name from list_proxy_targets. Omit for the account holder's own record. If MyChart is c… |
No output schema declared.
No examples provided.
How do I install the OpenRecord — MyChart for Claude MCP server?
OpenRecord — MyChart for Claude ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 2e466893856eb6f5ebf916af1f792e0c9b1561e8aebd68c64483ab04d3ca8a40; the commands to do that are on this page. If it does not match, do not open it.
mcpb · openrecord.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
2e466893856eb6f5ebf916af1f792e0c9b1561e8aebd68c64483ab04d3ca8a40
macOS / Linux
echo "2e466893856eb6f5ebf916af1f792e0c9b1561e8aebd68c64483ab04d3ca8a40 openrecord.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\openrecord.mcpb).Hash -eq "2e466893856eb6f5ebf916af1f792e0c9b1561e8aebd68c64483ab04d3ca8a40"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the OpenRecord — MyChart for Claude MCP server?
OpenRecord — MyChart for Claude is an MCP server listed in the public MCP registry as io.github.Fan-Pier-Labs/openrecord. Read and manage your Epic MyChart records: labs, meds, imaging, notes, messages, refills. This page covers its MCPB bundle (https://github.com/Fan-Pier-Labs/openrecord/releases/download/mcpb-v2.3.0/openrecord.mcpb).
Is the OpenRecord — MyChart for Claude MCP server safe to use?
OpenRecord — MyChart for Claude scores 36 out of 100 on VerifyMCP. 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 OpenRecord — MyChart for Claude MCP server expose?
OpenRecord — MyChart for Claude exposes 71 tools: check_pending_call, list_accounts, get_setup_widget, get_hospital_info, setup_account, and 66 more. Their descriptions and schemas cost roughly 12,797 tokens of context every time the server is loaded.
What did VerifyMCP test on the OpenRecord — MyChart for Claude MCP server?
VerifyMCP ran 13 checks on OpenRecord — MyChart for Claude, covering Source repository, Provenance, License, Maintenance and 9 more. 4 items could not be completed, a gap on our side rather than a finding about OpenRecord — MyChart for Claude: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.