io.github.orenyomtov/maccabi-health
Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
maccabi-healthclaude mcp add maccabi-health -- npx -y maccabi-health@0.1.6 mcp
{
"mcpServers": {
"maccabi-health": {
"command": "npx",
"args": [
"-y",
"maccabi-health@0.1.6",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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:
Analyze my blood test results, and tell me if my cholesterol is a problem
https://raw.githubusercontent.com/orenyomtov/maccabi-health/main/skills/maccabi-health/SKILL.md
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
npm install -g maccabi-health
maccabi-health login
maccabi-health labs --limit 10
Or, without a global install:
npx -y maccabi-health login
npx -y maccabi-health labs --limit 10
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
Use the `maccabi-health` CLI to read my Maccabi records.
Install with `npm install -g maccabi-health`.
Run `maccabi-health` for the command index, `maccabi-health help` for the full reference, and `maccabi-health help COMMAND --json` for one command's exact arguments.
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
claude mcp add maccabi-health -- npx -y maccabi-health mcp
codex mcp add maccabi-health -- npx -y maccabi-health mcp
gemini mcp add maccabi-health npx -y maccabi-health mcp
Cursor, in ~/.cursor/mcp.json:
{
"mcpServers": {
"maccabi-health": {
"command": "npx",
"args": ["-y", "maccabi-health", "mcp"]
}
}
}
maccabi-health mcp --http serves loopback Streamable HTTP with OAuth; see MCP.md.
Library
Install with:
npm install maccabi-health
Example usage:
import { connect, login } from "maccabi-health";
const pending = await login(idNumber);
await pending.sms();
const client = await pending.verify(smsCode);
const tests = await client.listTests({ year: 2025 });
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
| Read | Examples |
|---|---|
| Test results | Values, dates, units, ranges, historical comparisons and PDFs |
| Medication | Prescriptions, dispensing records and eligible PDFs |
| Medical records | Visit notes, vaccinations, referrals and summaries |
| Correspondence | Supported doctor inquiries, replies and documents |
| Billing | Quarterly reports and report PDFs |
| Imaging | Study list, series, and per-image metadata. Preview JPEGs and raw pixel files are CLI-only; only 8-bit ultrasound has been checked live |
| Other reads | Certificates, notifications, settings, and public provider search (often blocked by a bot challenge) |
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
Frequently asked questions
What is io.github.orenyomtov/maccabi-health?
Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs.
How do I install io.github.orenyomtov/maccabi-health?
It runs on your machine. In Claude Code: claude mcp add maccabi-health -- npx -y maccabi-health@0.1.6 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.orenyomtov/maccabi-health need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.orenyomtov/maccabi-health open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.orenyomtov/maccabi-health?
It is published by orenyomtov. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.