eclipse-beacon
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/beacon
What this is: eclipse-beacon is the MCP server edition of
Eclipse Beacon — Cyan Eclipse Technologies' insurance watcher: it
watches your household's policies, signals expiries before they
happen, and prepares the actions you approve.
What this is not: it does not insure, bind, cancel, pay, or advise. Beacon's personal edition is read/watch only, and acts only on the owner's own household data.
Use
$ pip install eclipse-beacon
$ eclipse-beacon # MCP server over stdio
Or run it as a container: ghcr.io/cyan-eclipse-technologies-llc/eclipse-beacon-mcp:0.1.0.
State lives in data/state.json beside the server (override with
ECLIPSE_BEACON_STATE). Python stdlib only; no network calls
anywhere in the code.
Tools (5)
| Tool | What it does |
|---|---|
policy_ingest |
Parse a declarations-page-style document (JSON or simple text) from a local file. Returns a draft + diff with per-field provenance. Propose-only unless confirm=true. |
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, proof deadlines, enrollment calendar) with severity, days-until, and the consequence of missing each. |
gap_report |
Read-only analysis: uncovered assets, duplicate coverage, premium spikes. Findings are signals with evidence — never verdicts, never advice. |
Honest scope
- v0.1 is phase B0 only (personal edition: policy graph + expiry radar). Renewal shopping, claims, binding, and the agency edition are explicitly out of scope.
- The shipped fixtures are synthetic — fictional carriers, synthetic people, invented policy numbers.
- The Vigil rule: alert windows may only be tightened (warn earlier), never loosened. The watcher never quietly gives you less warning.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for eclipse-beacon 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| eclipse_beacon-0.1.0.tar.gz | 28.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_beacon-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.5 kB
Release files / eclipse_beacon-0.1.0.tar.gz
| Download URL | eclipse_beacon-0.1.0.tar.gz |
|---|---|
| Size | 28.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5068d67c169bd4b236a46d533cdcaee078208412549de46e356c5f2a43ea1200
|
|
BLAKE2b-256 checksum How to use checksums |
1e8ef1e4638352647c3f00d8fd44d722177524ec9eeca2d88bf06526a1681bfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / eclipse_beacon-0.1.0-py3-none-any.whl
| Download URL | eclipse_beacon-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0e4c86d2e50f64975b4b883302f7006e8aaa6b908907e002c6ff0a28b2c6d91
|
|
BLAKE2b-256 checksum How to use checksums |
10e7da14916e7447f4774d4f3d5ff3b69d298a3c5f5537c603d07e5355726dfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for eclipse-beacon 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for eclipse_beacon-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
