Eclipse Beacon MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026

The insurance watcher — signals your policies' expiries before they happen. It does not insure

The publisher's own server: RealGeeks Company Registry

Overview

AI-generated overview

Local MCP server that builds a household insurance policy graph from local files and reports upcoming expiries, renewals and coverage gaps.

What you can do
  • Ingest policy declarations pages and household profiles from local files, returning drafts with per-field provenance and writing only when confirmed
  • List and read policies with key dates, declared assets and persons, and current alert windows
  • Report ranked upcoming events such as renewals, premium due dates, grace-period ends and proof deadlines, each with severity, days remaining and consequence
  • Analyse coverage gaps read-only: assets without a policy, duplicate coverage, and premium spikes versus the prior term
  • Append hash-chained receipts for ingests, merges and reports, and verify the receipt chain
When to use it
Useful for a household that keeps health, auto, home and life policies as PDFs and paper and wants an assistant to track deadlines and flag missing or duplicated coverage before a lapse notice arrives. It is a read-and-watch tool, not a way to buy, bind, cancel or pay for insurance.
Requirements
Runs as a local stdio process on the desktop, started with uvx from the eclipse-beacon PyPI package or with python3 server.py; Python standard library only, no network calls. State is kept in data/state.json beside the server, overridable with the ECLIPSE_BEACON_STATE environment variable. No authentication or API keys are declared.
Before you install
Ingest writes to the local policy graph only when confirm=true, so unconfirmed proposals stay drafts. The store holds real household policy and asset data, which the README says should never be committed to a repository. Shipped fixtures are synthetic. The server does not insure, bind or advise, and its gap findings are signals rather than verdicts; enrollment calendar dates are flagged for verification.

Installation

In SourceWeft

  1. Open Eclipse Beacon MCP in the dashboard and add it to a workspace.
  2. 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

Eclipse Beacon MCP

Powered by Cyan Eclipse Technologies — https://cetech.ai

Eclipse Beacon — the insurance watcher: it watches your household's policies, signals expiries before they happen, and prepares the actions you approve. It does not insure, bind, or advise.

Why this exists

A household's insurance — health, auto, home, life — has no system of record. Policies live as PDFs in email and paper in a drawer, and expiries are usually discovered by a lapse notice. Beacon B0 is the watcher that fixes the first half of that: a local policy graph with provenance on every field, and an expiry radar that signals deadlines before they arrive.

Status — honest labels

v0.1.0, phase B0 only (personal edition: policy graph + expiry radar). Read/watch only. Local stdio transport, Python stdlib only, no network calls anywhere in the code, and the shipped fixtures are synthetic (fictional carriers, synthetic people, invented policy numbers). No certification claimed — bench pending.

Explicitly NOT in v0.1, by spec: renewal shopping, renewal prep, claims filing, proof delivery, binding, cancelling, paying — and the entire agency edition, which is gated behind counsel + licensing review. Binding, negotiating, and advising for others are state-licensed producer activities; Beacon's personal edition acts only on the owner's own household data, and B0 doesn't even do that — it watches.

Tools (5)

ToolWhat it does
policy_ingestParse a declarations-page-style document (JSON, or simple text dec page) from a local file. Returns a draft + diff with per-field provenance (source file, locator, confidence). Propose-only by default — nothing is written unless confirm=true. Also ingests household_profile JSON (asset/person declarations).
policy_listEvery policy in the graph with key dates, plus declared assets/persons and current alert windows.
policy_getOne policy in full, provenance included.
radar_reportRanked upcoming events: renewal (≤60d), premium due (≤14d), grace-period end, escrow/lender proof deadline, and static enrollment calendar entries (ACA / Medicare — dates move yearly, flagged [verify] on the surface). Each event carries severity, days-until, the consequence of missing it, and the provenance of the date it came from.
gap_reportRead-only analysis: assets with no covering policy, duplicate coverage on the same asset, premium spikes vs the prior term (default flag >15%). Findings are signals with evidence — never verdicts, never advice.

The Vigil rule (encoded + tested)

Alert windows are owner-configurable, but a change may only tighten a window — lengthen its lead time so Beacon warns earlier. Any attempt to loosen a window (warn later, narrower net) is rejected with the reason named. The watcher never quietly gives you less warning.

Receipts

Every ingest proposal, merge, radar run and gap run appends a hash-chained receipt to the store — append-only and machine-verifiable (verify_receipt_chain). Proposals are receipted too: the audit trail covers what was attempted, not just what landed.

Run it

bash
python3 server.py            # MCP over stdio, stdlib only, no dependenciespython3 smoke.py             # end-to-end smoke over real stdio (temp state)python3 -m unittest discover tests   # 17 tests

State persists in data/state.json beside the server (override with ECLIPSE_BEACON_STATE). data/ is gitignored — a real household's graph never belongs in a repo.

Fixtures

fixtures/ ships four synthetic policies — auto, homeowners, health, term life — each as an ACORD-shaped JSON dec page and an equivalent simple-text dec page (the two parse to identical drafts; a test proves it), plus household.json declaring the household's assets and persons — including one boat that no policy covers, so the gap report has something honest to find.

Roadmap (per spec)

  • B1 — gap watcher expansion + lapse guard (escalation before lapse; still no transactions).
  • B2 — mandate-gated action prep: renewal shopping packs, renewal prep, claims FNOL drafting, proof delivery — owner-approved, none binding.
  • B3 — agency edition: blocked on counsel + licensing review. Does not start before the gate clears.

License / attribution

A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

Source: README.md at commit cde91d4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.1LatestOct 29, 2026
  2. v0.1.0Oct 26, 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

Other Beacon integrations