Cyan Eclipse Meridian MCP — Cyan Eclipse Bazaar

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio

Certification scope

CERTIFIED(local, synthetic scope) — Eclipse Bazaar Test Bench 2026-10-26, standing card eclipse-meridian-mcp-2026-10-26-2.json (re-bench 1): 22 pass, 0 na of 22 checks. CEILING — read exactly: SYNTHETIC ONLY. No live PHI, no real EHR connection, and no live claim of any kind is certified. NO SIGNING CAPABILITY EXISTS IN THIS PRODUCT: the surface is exactly the 19 specced Core tools with zero finalize-class tools; the re-bench probed 14 finalize/sign aliases via tools/call (all unknown-tool), ran a byte-for-byte import probe on a live draft (no clinician_sign attribute; the draft stays UNSIGNED_DRAFT), and swept every shipped file — no sign-capable path exists under any name, and the clinician-sign simulator exists only as bench equipment under tests/. The prior card eclipse-meridian-mcp-2026-10-26.json (FAILED — 23 pass / 6 fail) is retained unedited; defects B-MER-1..5 are all CLOSED in this re-bench (sign-path removal, refusal-naming ruling, per-practice hash-chain partition, refusal sealing, plus the observation item). P1 GATES — all still closed: HIPAA counsel review, an executed BAA, and a design partner are required before any live phase; the Bridge already refuses live PHI without a BAA (BAA_REQUIRED, no break-glass). No prescribing surface exists in any phase. N-CHECK: PASS, carried from the 2026-10-26 bench (not re-run; the fix round changed enforcement within the same fused mechanism — gate / pin / sealed reads — and removed the sign path outright).

What it does

Jurisdiction-gated encounters: licensure × consent set × mandate verify AT ENCOUNTER TIME against the patient's per-encounter attested location — license re-verified per encounter, never cached; a location change between booking and start re-runs the full gate (JURISDICTION_MISMATCH / CONSENT_SET_INCOMPLETE); jurisdiction rules are versioned counsel-signed DATA packs, never code constants
Note-integrity pin: SI drafts live cryptographically OUTSIDE the record (UNSIGNED_DRAFT) until the treating clinician signs the exact canonical fingerprint; post-signature change is a new version + addendum, never a silent edit
PRODUCT LAW: no note_finalize-class tool exists on the surface — signature is the clinician's act, never an agent capability — and no prescribing surface exists in any phase
Minimum-necessary PHI reads: purpose-declared, mandate-scoped field-class projection enforced server-side; every read granted or refused seals a 164.312(b)-shaped hash-chained access record, practice-held and offline-verifiable; the Bridge refuses live PHI without an executed BAA + complete flow-down inventory (BAA_REQUIRED, no break-glass)

Tools

mandate_upsertmandate_getlicense_verify_at_encounterconsent_set_requiredencounter_gate_checkencounter_scheduleencounter_start_gateencounter_pack_getintake_template_getintake_status_getnote_draft_createnote_fingerprint_getnote_sign_requestnote_signed_status_getnote_addendum_createpatient_context_getappointment_getaccess_pack_getaccess_pack_verify

Problems it addresses

My telehealth agents schedule across state lines, and I need licensure and consent verified at encounter time against where the patient actually is — not cached from intake
I need SI-drafted notes to stay cryptographically outside the record until the treating clinician signs the exact fingerprint — and no tool anywhere that lets an agent finalize one
When compliance asks who read which PHI fields and why, I need a sealed, hash-chained access record per read — granted or refused — that verifies offline

Not tested

Live PHI of any kind — P0 is synthetic-only by spec; no live claim exists until every P1 gate in spec §12.2 clears (HIPAA counsel + executed BAA + design partner)
Any real EHR/platform adapter — the P0 Bridge is the HAPI FHIR sandbox stand-in only; no vendor adapter is built
Clinician signing itself — by design: no signing capability exists in the product; the sign simulator is bench equipment in tests/ only, never a product surface (spec C3)

Bench scorecard: test-bench/results/eclipse-meridian-mcp-2026-10-26-2.json

Evaluation-intake listing

This listing records the tool's place in the Bazaar's evaluation and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope, and not-tested items included. It is not sold on this site, and its presence in the catalog is not a claim beyond that evidence. The service behind every verdict is the bench: what a bench run buys →