
Maccabi Health
io.github.orenyomtovPublished by GitHub account orenyomtovv0.1.6Updated Oct 24, 2026
Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs.
Overview
Reads your own Maccabi Healthcare records — labs, prescriptions, visits, referrals and PDFs — so an assistant can review and explain them.
- What you can do
- Read lab test results with values, dates, units, ranges, historical comparisons and PDFs
- Read prescriptions, dispensing records and eligible medication PDFs
- Read visit notes, vaccinations, referrals, summaries and doctor correspondence
- Read billing reports, imaging study lists and metadata, certificates and notifications
- Sign in via ID number and SMS code, with an optional browser login and session export
- When to use it
- Useful when you want an assistant to help interpret your own Maccabi lab results, prescriptions or visit history, or to pull the original documents behind them. It is unofficial and only covers one Israeli health fund.
- Requirements
- Runs locally via npm (Node.js) as a stdio process, or as a loopback HTTP server with OAuth. Needs your Israeli ID number and access to the phone that receives the SMS login code. Sessions expire one hour after login; a background keep-alive can be started or skipped.
Installation
In SourceWeft
- Open Maccabi Health in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Maccabi Health
Ask an AI assistant for a second look at your lab results, scans, doctor visits, messages, referrals, and prescriptions.
Read your records from Maccabi Healthcare Services, the Israeli health fund, through a CLI or an AI assistant: laboratory history, doctor correspondence, visits, prescriptions, referrals, and supported original PDFs.
Unofficial and unaffiliated with Maccabi. You need your ID number (תעודת זהות) and access to the phone that receives the login code via SMS.
Getting started
Copy and paste this to your agent:
Agents like Claude Code, Cowork, Codex, Cursor, Instinct, Muse, and ChatGPT Work can follow that.
Another option to get started is to run npx skills add orenyomtov/maccabi-health which installs that skill into Cursor, Claude Code, Codex and other local agents.
Install and sign in
Or, without a global install:
maccabi-health login asks for your ID and the SMS code in the terminal. If an agent prefers the user to sign in directly in the browser, maccabi-health login --http prints a URL that the user can be redirected to to login instead, and it writes to the same session file that the CLI uses.
If maccabi-health is not on your PATH after a global install, use the absolute path to the bin or stick with npx.
Sessions expire
Maccabi ends every session an hour after login, activity or not. A finished maccabi-health login starts a background keep-alive for that hour (a renewal every 240 seconds) and then returns, so later commands keep working until the hour is up. maccabi-health login --no-keep-alive skips it. maccabi-health logout stops it. The background process cannot extend the hour. Measurements are in SESSION-LIFETIME.md.
Privacy
Every record you read here is real medical data. Anything you hand to an assistant becomes part of that model's context and goes wherever that model runs.
Agent with a shell
The CLI is usually the better surface there: no tool-cap fights, and JSON out of a pipe is something an agent can already filter and loop over.
MCP
Cursor, in ~/.cursor/mcp.json:
maccabi-health mcp --http serves loopback Streamable HTTP with OAuth; see MCP.md.
Library
Install with:
Example usage:
pending.phones lists the SMS numbers; pass an index to sms() when there is more than one. A wrong code ends the attempt.
You can save await client.exportSession() and open it later with connect(session).
The methods are the same reads as the CLI.
Capabilities
See the full capability reference.
Something not working?
Fix the bug and send a pull request. That is better than only opening an issue: each account has different records, so the maintainer often cannot reproduce what you saw. See Contributing.
Open an issue if you cannot fix it. Never paste medical records, ID numbers, cookies or session files. Security problems go through SECURITY.md.
All docs · Authentication · CLI guide · MCP transports · Changelog · API sources · Contributing · MIT license
Source: README.md at commit 1df6d61
Tools
0Version history
3- v0.1.6LatestSep 28, 2026
- v0.1.5Sep 27, 2026
- v0.1.2Sep 27, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts