myatriumhealth-mcp

io.github.chrischall/myatriumhealth-mcp

About myatriumhealth-mcp

myatriumhealth-mcp is an MCP server published by the GitHub account chrischall. MyAtriumHealth (Epic MyChart) records via your signed-in browser tab

It runs on your own machine: your AI client starts it from the npm package @chrischall/myatriumhealth-mcp at version 1.3.8.

It asks for one secret: MAH_PASSWORD. Give it a key with the least access that still works.

Version 1.3.8 was published on 20 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

VariableRequiredSecretDescription
MAH_WS_PORTNoNoOverride the fetchproxy WebSocket port (default 37149).
MAH_READ_ONLYNoNotrue refuses mah_reply_message sends (previews still work). Default false.
MAH_USERNAMENoNoMyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
MAH_PASSWORDNoYesPortal password. Both are required; setting only one falls back to the bridge (with a warning).
MAH_DOTENVNoNoPath to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
MAH_DEVICE_FILENoNoSession state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
FETCHPROXY_WS_HOSTNoNoBind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
FETCHPROXY_IDENTITY_DIRNoNoAbsolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Checks

CheckResultDetail
Source repository linkedPasshttps://github.com/chrischall/myatriumhealth-mcp
Version pinnedPassEvery package has an explicit version
Secrets requestedInfoAsks for 1 secret: MAH_PASSWORD
Known package registryPassAll packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownershipInfoName verified via GitHub account chrischall
Registry text aimed at the AIPassDescription and settings contain no hidden characters or instructions to the AI
Install scriptsPass@chrischall/myatriumhealth-mcp@1.3.8 runs nothing at install
Code red flagsPassRead 10 files in @chrischall/myatriumhealth-mcp@1.3.8: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AIPassNo hidden characters or instructions to the AI in 10 files, including comments and the README

Popularity & health: 60 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity10 / 40

1 GitHub stars, 248 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-22, last release 2026-10-20, 0 commits in 90 days.

Issue health15 / 15

16 closed of 16 issues.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 114 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry nameio.github.chrischall/myatriumhealth-mcp
PublisherGitHub account chrischall
How the name is verifiedName verified via GitHub account chrischall. The registry ties the name prefix to that account or domain; it does not check the code.
TypeLocal: runs on your machine from a package
Packagesnpm @chrischall/myatriumhealth-mcp 1.3.8 (stdio)
Version1.3.8
Published
Last updated
Source repositoryhttps://github.com/chrischall/myatriumhealth-mcp
WebsiteNone linked
CategoryBrowser automation (assigned by keyword rule, not by hand)

Related servers in Browser automation