Eclipse Beacon MCP Server
The insurance watcher — signals your policies' expiries before they happen. It does not insure
Eclipse Beacon MCP scores 55 (Fair), with no SPDX license recorded. It installs as a local process. It declares 5 tools. Filed under Uncategorized. Install configs are generated for 10 clients. Being listed in the registry is not the same as being vendor-official.
Fair trust
55 of 100 from six public signals. Nobody can buy a point.
- Listed in the official MCP registry.
- No license recorded.
License, quality and maintenance
Where the 55 comes from
22 + 20 + 0 + 0 + 10 + 3 = 55. Each factor is capped, so no single signal can carry a listing.
Active in the official MCP registry, plus a known vendor namespace.
Registry: 22 of 30 points.How recently the repository saw a commit or release.
Maintenance: 20 of 20 points.GitHub stars and weekly downloads, on a log scale.
Popularity: 0 of 20 points.A clear, OSI-style open-source license.
License: 0 of 10 points.Not archived, a secure install path, a pinned version.
Security: 10 of 10 points.A real summary, a README with depth, listed tools.
Docs: 3 of 10 points.Install
Pick your client, copy the config, paste it in.
Needs Cursor or VS Code installed on this device. The button opens the app and asks you to confirm before it adds the server.
{ "mcpServers": { "cyan-eclipse-technologies-llc-beacon": { "command": "uvx", "args": [ "eclipse-beacon" ] } }}
Environment variables
This server does not declare environment variables.
Tools5Tool docs quality grade C
All capabilitiesgap_reporttoolRead-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.
policy_gettoolOne policy in full, provenance included.
policy_ingesttoolParse 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=tru
policy_listtoolEvery policy in the graph with key dates, plus declared assets/persons and current alert windows.
radar_reporttoolRanked 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 sev
About
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)
| Tool | What it does |
|---|---|
policy_ingest | Parse 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_list | Every policy in the graph with key dates, plus declared assets/persons and current alert windows. |
policy_get | One policy in full, provenance included. |
radar_report | Ranked 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_report | Read-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
python3 server.py # MCP over stdio, stdlib only, no dependencies
python3 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.
Frequently asked questions
What is Eclipse Beacon MCP Server?
The insurance watcher — signals your policies' expiries before they happen. It does not insure
How do I install Eclipse Beacon MCP Server in Claude Desktop, Cursor, or VS Code?
Pick your client in the Install section on this page and copy the generated config into the client's config file. Step-by-step guides: Claude Desktop, Cursor, and VS Code. Eclipse Beacon MCP Server runs locally from the PyPI package eclipse-beacon with the command uvx eclipse-beacon.
Does Eclipse Beacon MCP Server support remote (HTTP) connections?
No remote endpoint is listed for Eclipse Beacon MCP Server. It runs locally on your machine over stdio, started by your MCP client.
What tools does Eclipse Beacon MCP Server provide?
Eclipse Beacon MCP Server provides 5 tools, including gap_report, policy_get, policy_ingest, and policy_list. See the full tool list for descriptions and parameters.
How is Eclipse Beacon MCP Server's trust score calculated?
Eclipse Beacon MCP Server scores 55 out of 100 (Fair). The score adds six capped public signals: registry status, maintenance, popularity, license, documentation, and security. Nobody can pay for points. Read the methodology for the full formula.
Reviews
No reviews yet—Be the first to review
No published reviews yet. Used it? Tell the next person how it went.
Sign inA verified email is required to review this server.
Add badge to your README
Paste either snippet into the repository README. The image links to this listing.