Skip to content
MCP server

Eclipse Meridian MCP

Governed telehealth operations MCP server for synthetic-scope encounter, note and PHI

Platforms
API
Version
0.1.0
Listing updated
today

Similar MCP servers

About Eclipse Meridian MCP

Eclipse Meridian MCP is an MCP server for health and science. It is available on API.

The README and registry entry describe Meridian as a governed layer for telehealth operations, where encounters only run after licensure, consent and mandate checks pass against the patient's attested location. Drafted clinical notes are kept outside the record until the treating clinician signs the exact fingerprint, and every PHI read, granted or refused, is written to a hash-chained access record.

According to the Bazaar catalog entry, the product is in a synthetic scope: it works without live PHI or a real EHR connection, and it has no note-signing capability and no prescribing surface. The catalog says a production use would need HIPAA counsel, a business associate agreement and a design partner first.

The server is listed as part of the Cyan Eclipse family of governed MCP tools and is benched as a local, synthetic-scope build. Transport and package details are not given in the registry entry.

Tools this server provides (19)

Taken from the project documentation; the running server may differ.

mandate_upsert
Creates or updates a governing mandate.
mandate_get
Retrieves a mandate.
license_verify_at_encounter
Verifies licensure at encounter time.
consent_set_required
Sets required consent for an encounter.
encounter_gate_check
Checks whether an encounter may proceed.
encounter_schedule
Schedules an encounter.
encounter_start_gate
Gates the start of an encounter.
encounter_pack_get
Retrieves an encounter evidence pack.
intake_template_get
Retrieves an intake template.
intake_status_get
Retrieves intake status.
note_draft_create
Creates a draft clinical note.
note_fingerprint_get
Retrieves a note fingerprint.
note_sign_request
Requests a clinician signature on a note.
note_signed_status_get
Retrieves signed status of a note.
note_addendum_create
Creates a note addendum.
patient_context_get
Retrieves patient context.
appointment_get
Retrieves an appointment.
access_pack_get
Retrieves an access evidence pack.
access_pack_verify
Verifies an access evidence pack.

What it does

Encounter gating
Encounters are checked for licensure, consent and mandate at encounter time against the patient's attested location before they start.
Clinician-signed notes
Drafted notes stay separate from the record until the treating clinician signs the exact fingerprint.
Purpose-declared PHI reads
Minimum-necessary patient data reads must declare a purpose, and every read is logged in a hash-chained access record.
Synthetic-only scope
The build works only with synthetic data and has no live EHR connection, according to the catalog.

Good for

  • Prototyping governed telehealth encounter workflows with synthetic patient data
  • Testing how an agent drafts clinical notes that a clinician must sign before they enter the record
  • Reviewing an audit trail of every PHI access, including refused requests

Eclipse Meridian MCP FAQ

Can Meridian sign clinical notes?

No. The catalog states that no signing capability exists in this product in any phase, and there is no note_finalize-class tool.

Does it connect to a live EHR or handle real patient data?

The catalog describes it as synthetic scope only, with no live PHI and no real EHR connection.

What is required before live use?

The catalog says a P1 release requires HIPAA counsel, an executed business associate agreement and a design partner.

What are the best alternatives to Eclipse Meridian MCP?

The closest alternatives to Eclipse Meridian MCP are Last EHR — Medplum, Insync MCP and Neuro MCP.

Where this comes from

  • Description: written from the project's website and its MCP Registry entry.

How AIPoweredBot checks servers