# io.github.orenyomtov/maccabi-health (npm · maccabi-health)

Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- npm · `maccabi-health`: 77/100 (this document), [markdown](https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health.md), [page](https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health)

## Channel facts

- Registry: `npm`
- Package: `maccabi-health`
- Version: `0.1.6`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 33 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to orenyomtov/maccabi-health).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 46/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5421 tokens (~139/item across 39 items; 38 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 16% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.orenyomtov/maccabi-health MCP server?

io.github.orenyomtov/maccabi-health runs locally as an npm package, launched with npx -y maccabi-health. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add orenyomtov-maccabi-health -- npx -y maccabi-health
```

### Cursor

```json
{
  "mcpServers": {
    "orenyomtov-maccabi-health": {
      "command": "npx",
      "args": [
        "-y",
        "maccabi-health"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "orenyomtov-maccabi-health": {
      "command": "npx",
      "args": [
        "-y",
        "maccabi-health"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add orenyomtov-maccabi-health -- npx -y maccabi-health
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orenyomtov-maccabi-health": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "maccabi-health"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add orenyomtov-maccabi-health --command npx --arg -y --arg maccabi-health
```

### Hermes

```yaml
mcp_servers:
  orenyomtov-maccabi-health:
    command: "npx"
    args: ["-y", "maccabi-health"]
```

### Netclaw

```json
{
  "McpServers": {
    "orenyomtov-maccabi-health": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "maccabi-health"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add orenyomtov-maccabi-health -t stdio -c npx -a -y maccabi-health
```

### Other

```json
{
  "mcpServers": {
    "orenyomtov-maccabi-health": {
      "command": "npx",
      "args": [
        "-y",
        "maccabi-health"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 76, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-01 (score 75, 0)

- [functional regression] Security disclosure: pass → unverified

### 2026-09-29 (score 75, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.96

### 2026-09-28 (score 48, −26)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Dependency health: 0.96 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.5 → 0.1.6
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 74)

First indexed and scored.

## MCP tools (38)

### `maccabi_capabilities` (~80 tokens)

Start here. Describes what this server can read, the worked journeys from an empty conversation to a result, how row references and the `next` list work, and where coverage stops. Needs no account and makes no upstream request. Read it once before planning a sequence of calls; individual tool results then carry their own `next` steps.

### `maccabi_directory_specialties` (~89 tokens)

List the specialties and services the public provider directory can be searched by. Takes a category: `doctors`, or `labs-and-therapists` for labs, institutes and therapists. Returns `field` keys and their Hebrew labels; a search in the same category takes one of those keys. Public catalog: no account, session or cookies.

Input parameters:

- `category` (string, required)

### `maccabi_directory_cities` (~57 tokens)

List the city keys the public provider directory accepts for a category, with their Hebrew labels. A search takes one of these keys as its optional `city`. Public catalog: no account access.

Input parameters:

- `category` (string, required)

### `maccabi_directory_search` (~129 tokens)

Search the public provider directory. Needs a category and a `field` key from maccabi_directory_specialties; optional `city` key, provider `name` and upstream `page`. Returns matching providers with names, addresses and phone numbers, each row carrying a `ref` for maccabi_detail. Page bounds are checked against a freshly fetched catalog. No account cookies, no booking links, no retries.

Input parameters:

- `category` (string, required)
- `city` (string)
- `field` (string, required)
- `name` (string)
- `page` (integer)

### `maccabi_login_start` (~137 tokens)

Begin a Maccabi sign-in and send one SMS code to the member's registered phone. The ID number passes through this conversation and into model context; running `maccabi-health login` in the member's own terminal keeps it out, so offer that first. If several SMS numbers are registered and phone is omitted, the numbered options are returned and no SMS is sent; call again with phone set to one of them. One SMS per call, never resent automatically. The challenge expires ten minutes after this call. Finish with maccabi_login_verify.

Input parameters:

- `id` (string, required)
- `phone` (integer)

### `maccabi_login_verify` (~96 tokens)

Finish the sign-in started by maccabi_login_start using the six-digit SMS code, and save the session to protected local storage. The code passes through this conversation and into model context. One attempt only: a wrong code ends the challenge and maccabi_login_start must be called again, because repeated attempts lock the Maccabi account. After this succeeds, every account tool works.

Input parameters:

- `code` (string, required)

### `maccabi_login_status` (~71 tokens)

Report whether a session is saved, a started sign-in is still waiting for its SMS code and how many seconds it has left, or nothing is signed in. Call this first when an account read fails and you are unsure why. Local state only: no upstream request, no SMS, no credentials.

### `maccabi_logout` (~65 tokens)

Delete the locally saved session and any sign-in still waiting for its code. Local only; it does not sign the member out of the Maccabi website or revoke anything upstream. Signing back in costs the member another SMS, so do not call it to clear an error.

### `maccabi_renew_session` (~83 tokens)

Renew the current owner session once and persist the refreshed cookies, to keep a long-lived server from going idle. Not a clinical read: it changes server-side expiry state. It guarantees no extension duration or continued authentication and cannot reset an open browser's idle/logout countdown. Stops on the first error or reauthentication, with no retries, SMS or background timer.

### `maccabi_detail` (~325 tokens)

Read the full record behind any row a list tool returned. The row is named by its `ref` alone, so identifiers from two different rows can never be paired. What comes back follows the row: a test row gives its laboratory values; a visit, inquiry, administrative request, upcoming appointment or directory provider gives its detail; a vaccination group gives its dose rows; a prescription gives its listed pharmacy alternatives; an imaging study gives its series and images. The other arguments only narrow what is already inside that row, and every one of them is copied verbatim from a payload you already have: `test_id` turns a test, latest-results or followed-results ref into one analyte's history, `series_instance_uid` with `sop_instance_uid` turn an imaging-study ref into one image's DICOM metadata, and `offset`/`limit` page the two details that are a list of rows, a vaccination group's doses and a prescription's alternatives - every other ref reads one record and returns it whole, so the pair is refused there rather than ignored. None of them selects a different record: each is checked against the freshly fetched payload the ref names, and a value that belongs to another row or another study is refused rather than fetched. Rows whose only content is a document say so and name maccabi_document.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `ref` (string, required)
- `series_instance_uid` (string)
- `sop_instance_uid` (string)
- `test_id` (string)

### `maccabi_document` (~368 tokens)

Read the original PDF behind any row a list tool returned, embedded in the reply (maximum 2 MiB). Takes that row's `ref`, which already carries the date range, as-of date, period or parent id the download needs, so none of that has to be reassembled. Rows that carry exactly one document need only the ref: certificates, type-1 and type-2 mailings, additional-information entries, hospital reports, quarterly billing reports, nursing-insurance reports, prescriptions and referrals. `variant` chooses between documents where a row has several: a test row offers attached_document (default), laboratory_report and english_covid_report, and a visit offers its summary. `reference` selects one attachment listed inside a row - a visit document, an inquiry document, an administrative attachment, a mailing tutorial - using a pdf_reference or attachments[].reference value from that row's own detail. `test_id` narrows a lab ref to one analyte, whose attached_document, comparison_list and comparison_graph then apply. `irregular_only` uses the source's own print checkbox on a laboratory report, not any medical judgement of this server's. All four narrow the ref rather than redirecting it, and a selector the row has no use for is refused rather than dropped: `reference` is looked up in the parent record's own freshly fetched attachment list and never becomes a URL on its own, so a reference taken from another row is refused rather than downloaded. The PDF may print identity details Maccabi put there; its URI is an inline resource, not a download link.

Input parameters:

- `irregular_only` (boolean)
- `ref` (string, required)
- `reference` (string)
- `test_id` (string)
- `variant` (string)

### `maccabi_report` (~162 tokens)

Read one of the account-wide original PDFs - the ones that cover the whole record rather than a single row, so they need no reference (maximum 2 MiB). latest_labs is the latest-results report and accepts irregular_only, which ticks the source's own print checkbox; followed_labs is the report for the tests the member follows; allergies is the sensitivity report; vaccination_certificate is the vaccination certificate; english_medical_summary is the English medical summary, which needs the member's English-name and passport profile fields already filled in; purchased_medications is the purchased-medication report. For a document belonging to one row, use maccabi_document. These PDFs print identity details.

Input parameters:

- `document` (string, required)
- `irregular_only` (boolean)

### `maccabi_account` (~291 tokens)

Read one section of the signed-in member's own account record; `section` says which. `profile` is their name, sex and date of birth, which is how you confirm whose record the rest of these tools are reading. `contact_details` is the email address, phone numbers and postal address Maccabi holds. `authorized_users` is who else may view this account, with their names, identification numbers and authorization end dates, plus whether a new authorization can currently be created. `notification_settings` is which notification groups, services and channels the member is registered for, which are restricted, and the contact fields they would be sent to - the settings page, not the messages, which are maccabi_mailings. `payment_methods` is the payment-authorization summary with the bank, card type and last four digits the source shows. The member's national ID, the upstream credentials and full account numbers are excluded, and there is no family data or directory lookup here. The observed account-access state was creation-available; populated authorized users and the notification read are source-backed and offline-tested. Every section is a read: nothing is saved, granted, extended, revoked or paid, nothing is applied to a family member, and the account being read is never switched. For the payer account's outstanding totals use maccabi_payer_account_totals.

Input parameters:

- `section` (string, required)

### `maccabi_medical_recommendations` (~57 tokens)

Read the recommendation text and table from the legacy medical-recommendations page, in the source's own clinical wording. Only the one captured single-section layout is supported, and this is not a complete history of recommendations.

### `maccabi_medical_summary` (~57 tokens)

Read the legacy summary page that pairs selected medications with selected laboratory results, as text and tables in the source's wording. This is neither a complete medical history nor the English medical summary PDF, which maccabi_report returns.

### `maccabi_hospital_visits` (~194 tokens)

List hospital and emergency-room admissions. `as_of` is required and anchors the lookback the source page applies (three years in the captured settings): it is the end of the window, so pass today's date for the current one. An optional paired from/to narrows it and must end no later than as_of. Rows carry a `ref` for maccabi_document, which returns the admission's original report. Retention beyond the lookback is unverified.

Input parameters:

- `as_of` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `from` (string): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `limit` (integer)
- `offset` (integer)
- `to` (string): A calendar date written YYYY-MM-DD, for example 2026-01-31.

### `maccabi_mailings` (~207 tokens)

List the letters, status notices and tutorials Maccabi sent the member, in a required date range. Type 1 is a letter and type 2 a status notice, each with a `reference`; type 3 is a set of tutorials whose PDFs are the tutorials[].pdf_reference values. Rows carry a `ref` for maccabi_document; for a type-3 row pass one of its tutorial references as `reference` as well. Webpage and video links are returned without being fetched. For the notification settings page use maccabi_account with section=notification_settings. Types 2 and 3 are source-backed and offline-tested. No mark-read.

Input parameters:

- `from` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `limit` (integer)
- `offset` (integer)
- `to` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.

### `maccabi_prescriptions` (~146 tokens)

List the member's prescriptions and what has been dispensed against them. Optional `status` (all, valid, history, purchased, expired, renewable) and `permanent` filter the same fetched response locally and mark the result as a filtered subset. Rows carry a `ref`: maccabi_document returns the prescription PDF for a digital prescription, and maccabi_detail lists the pharmacy alternatives the source offers for it. `renewable` reports eligibility only and never requests a renewal; a past purchase does not establish current use.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `permanent` (boolean)
- `status` (string)

### `maccabi_referrals` (~112 tokens)

List the member's referrals. An optional paired from/to uses the source's own date filter. Rows carry a `ref` for maccabi_document, which returns the referral's original PDF.

Input parameters:

- `from` (string): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `limit` (integer)
- `offset` (integer)
- `to` (string): A calendar date written YYYY-MM-DD, for example 2026-01-31.

### `maccabi_medical_certificates` (~135 tokens)

List medical certificates - sick notes, fitness confirmations and the like - in a required date range, with the issuing clinician, specialization and validity dates. Rows carry a `ref` for maccabi_document, which returns the certificate's original PDF. For the vaccination certificate use maccabi_report instead.

Input parameters:

- `from` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `limit` (integer)
- `offset` (integer)
- `to` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.

### `maccabi_additional_information` (~172 tokens)

List the extra material attached to the member's sessions in a required date range: the portal's 'additional information' feed of handouts, explanatory pages and videos, with the practitioner and specialization behind each. Type-1 entries are downloadable and their rows carry a `ref` for maccabi_document; webpage and video entries are listed but never fetched, and no raw URL is returned. Only an empty account response was ever captured, so populated rows and their downloads are unvalidated live.

Input parameters:

- `from` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.
- `limit` (integer)
- `offset` (integer)
- `to` (string, required): A calendar date written YYYY-MM-DD, for example 2026-01-31.

### `maccabi_tests` (~162 tokens)

List every test result the member has - laboratory panels, imaging, and other result types - newest first, with the test names, execution and result dates. This is the entry point for anything test-shaped. Optional `year` filters execution dates locally. Every row carries a `ref`: maccabi_detail reads a laboratory row's values, units and reference ranges, and maccabi_document returns whatever original document the row has. `has_document` says whether there is one; imaging rows have none, because their scans live in the external viewer that maccabi_imaging_studies reaches. `categories` describes the row types the source recognises.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `year` (integer)

### `maccabi_imaging_studies` (~128 tokens)

List the member's imaging studies: the test rows whose scans are held in the external MedDream viewer Maccabi hands them off to, rather than as an attached document. Each row carries a `ref` for maccabi_detail, which reads the study's series and images from that viewer. The row's request_id is the study's DICOM Study Instance UID, verified byte-for-byte against a live handoff. These rows have no attached document, so maccabi_document correctly refuses them.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_latest_labs` (~137 tokens)

Read the member's most recent laboratory results, grouped as the source groups them, keeping every value, unit, date and message. The result carries one `ref` for the whole latest-results view: pass it to maccabi_detail with any group_values[].test_id for that analyte's history, which can reach further back than this list, or to maccabi_document for that analyte's own attached result. maccabi_report returns the whole latest-results PDF. Paging selects groups, not individual rows. This is not a complete history.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_followed_labs` (~120 tokens)

Read the laboratory tests the member follows, with their counter and the source's selection options, as one complete envelope. The result carries one `ref` for the followed view: pass it to maccabi_detail with any followed test's test_id for that analyte's history, or to maccabi_document for its attached result or comparison PDF. maccabi_report returns the whole followed-results PDF. The overall output cap applies and there is no local slicing. Source-backed and offline-tested. It never changes which tests are followed.

### `maccabi_vaccinations` (~96 tokens)

List the member's vaccinations grouped by vaccine, with the source's group codes, labels, dose counts and first/last dates. Each row carries a `ref` for maccabi_detail, which lists that group's individual dose records. maccabi_report returns the vaccination certificate PDF. This is group-level data and not a complete immunization record.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_allergies` (~114 tokens)

List the member's recorded drug sensitivities and intolerances - what Maccabi's own record calls sensitivities. maccabi_report returns the sensitivity report PDF. The account capture was empty, so the populated projection is labeled source.schemaEvidence=frontend-field-projection and an unknown shape fails rather than being guessed at. An empty list does not establish absence of allergies: it means this record holds none, which is not the same thing.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_administrative_requests` (~120 tokens)

List the member's administrative case timeline: approvals, reimbursement claims and funding commitments, with their status. These are the paperwork requests, not medical questions to a doctor - those are maccabi_doctor_inquiries. Each row carries a `ref` for maccabi_detail, which reads the correspondence and its eligible attachments. The live account list was empty, so populated rows are source-backed and offline-tested. Nothing is approved, paid, submitted or marked read.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_nursing_insurance_reports` (~87 tokens)

Read the catalog of annual nursing-insurance reports shown on the member's billing page, with their periods, production dates and view labels. Each report carries a `ref` for maccabi_document, which returns the original annual PDF. No individual insured-person attribution and no claim of complete history; the overall output cap applies and there is no period or person selector.

### `maccabi_billing_reports` (~106 tokens)

Read the catalog of quarterly billing reports, with the periods available, the period currently selected, and each report's production date and view label. Each report carries a `ref` for maccabi_document, which returns the original quarterly PDF and already knows which period it belongs to. Optional `period` must exactly match one of the source page's own availablePeriods values. This is the catalog's first page, not itemized charges.

Input parameters:

- `period` (string)

### `maccabi_payer_account_totals` (~108 tokens)

Read the outstanding totals for the payer account this member belongs to, from the source's fixed other-payer branch. These are account-level figures labeled source.scope=payer-account-aggregate: they are not this member's personal debt, and the source attributes neither an individual debtor nor a currency. Do not present them as what the member owes. For how this member's own charges are paid, use maccabi_account with section=payment_methods. No payment is made.

### `maccabi_doctor_inquiries` (~132 tokens)

List the medical inquiries the member sent to a doctor or clinic office, with their status. These are clinical questions and their answers, not reimbursement or approval paperwork - that is maccabi_administrative_requests. Each row carries a `ref` for maccabi_detail, which reads the patient and clinician text. An automatic_sick_permit row is list-only: its document is the row's own pdf_reference, passed to maccabi_document as `reference`. Nothing is submitted, cancelled, answered or marked read.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_past_visits` (~145 tokens)

List the member's past visits - who was seen, when, and for what service. For appointments that have not happened yet use maccabi_upcoming_appointments. Each row carries a `ref`: maccabi_detail reads the visit and the documents attached to it, and maccabi_document returns its summary PDF where has_summery_file is true - that is Maccabi's own spelling of the list field and it is kept exactly as sent, while maccabi_detail reports the same fact on the visit as has_summary_pdf. This does not establish complete lifetime history.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_upcoming_appointments` (~120 tokens)

List the member's future appointments, with the date, provider and service. For visits that already happened use maccabi_past_visits. A row for an ordinary provider carries a `ref` for maccabi_detail, which reads that provider's contact details and the visit instructions. The captured account list was empty, so populated rows are a frontend-derived projection retaining source.schemaEvidence and are offline-tested only. Nothing is booked, cancelled or consented to.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_assigned_doctor` (~123 tokens)

Read which doctor the member was assigned to at a given moment - the ascribed family physician. `as_of` is the moment being asked about, so pass today's date and time for the current assignment. It is timezone-free calendar text, YYYY-MM-DDTHH:mm:ss, and is used exactly as written with no timezone interpretation added.

Input parameters:

- `as_of` (string, required): A timezone-free calendar moment written YYYY-MM-DDTHH:mm:ss, for example 2026-01-31T09:00:00, used exactly as written.

### `maccabi_recent_providers` (~92 tokens)

List the providers and clinics this adult member has had appointments with recently, with clinic addresses. Each row carries a `ref`: maccabi_detail reads the clinic, schedule and provider record, maccabi_appointment_eligibility says whether booking is permitted, and maccabi_clinic_availability reads the first free window.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `maccabi_appointment_eligibility` (~54 tokens)

Check whether this member may book an appointment with one provider from maccabi_recent_providers, using that row's `ref`. It reports eligibility and books nothing.

Input parameters:

- `ref` (string, required)

### `maccabi_clinic_availability` (~101 tokens)

Read the first clinic window one provider from maccabi_recent_providers has free, using that row's `ref`. It opens a scheduling conversation upstream and chooses clinic mode, then stops before any date or time is selected, so it is neither side-effect-free nor idempotent and it never books. Only the first observed window is covered, and an unknown dialogue branch fails rather than being guessed at.

Input parameters:

- `ref` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health#diagnostics

## Score history

- 2026-10-04: 77
- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 75
- 2026-09-29: 75
- 2026-09-28: 48
- 2026-09-27: 74

## Common questions

### What is the io.github.orenyomtov/maccabi-health MCP server?

io.github.orenyomtov/maccabi-health is an MCP server listed in the public MCP registry as io.github.orenyomtov/maccabi-health. Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs. This page covers its npm package (maccabi-health).

### Is the io.github.orenyomtov/maccabi-health MCP server safe to use?

io.github.orenyomtov/maccabi-health scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.orenyomtov/maccabi-health MCP server expose?

io.github.orenyomtov/maccabi-health exposes 38 tools: maccabi_capabilities, maccabi_directory_specialties, maccabi_directory_cities, maccabi_directory_search, maccabi_login_start, and 33 more. Their descriptions and schemas cost roughly 4,978 tokens of context every time the server is loaded.

### Is the io.github.orenyomtov/maccabi-health MCP server still maintained?

io.github.orenyomtov/maccabi-health is still listed as active in the MCP registry. We last reached this channel on 4 October 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.orenyomtov/maccabi-health MCP server under?

io.github.orenyomtov/maccabi-health declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/maccabi-health
- Socket report: https://socket.dev/npm/package/maccabi-health
- Repository: https://github.com/orenyomtov/maccabi-health
- Changelog RSS feed: https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health.xml
- Changelog JSON feed: https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health.json
- HTML version of this page: https://verifymcp.io/servers/orenyomtov-maccabi-health/maccabi-health