Eclipse Beacon MCP
PYPI · ECLIPSE-BEACON
The insurance watcher — signals your policies' expiries before they happen. It does not insure
Available components
Last scanned (22 hours ago)
Scores higher than 67% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-beacon-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 264 tokens (~52/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +10
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/eclipse-beacon@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-beacon-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-beacon-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0 |
| Rekor log index | 3517560614 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5068d67c169bd4b236a46d533cdcaee078208412549de46e356c5f2a43ea1200 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gap_report ~40
Read-only gap analysis: uncovered assets, duplicate coverage, premium spikes vs prior term (default flag >15%).
| Name | Type | Req | Description |
|---|---|---|---|
| spike_threshold_pct | number | – | – |
No output schema declared.
No examples provided.
policy_get ~26
One policy in full, including per-field provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
No output schema declared.
No examples provided.
policy_ingest ~77
Ingest a declarations-page-style document (JSON or simple text) from a LOCAL file path. Returns a draft + diff with per-field provenance. DEFAULT IS PROPOSE-ONLY: nothing is written unless confirm=true. Also ingests household_profile JSON (asset/person declarations).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
policy_list ~29
List every policy in the household graph with key dates, plus declared assets/persons and current alert windows.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
radar_report ~92
Expiry radar: ranked upcoming events (renewal <=60d, premium due <=14d, grace end, escrow proof, enrollment windows [verify]) with severity and consequence. Optional as_of (YYYY-MM-DD) and windows overrides — windows may only be TIGHTENED (longer lead), never loosened (Vigil rule).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | – |
| windows | object | – | – |
No output schema declared.
No examples provided.
How do I install the Eclipse Beacon MCP server?
Eclipse Beacon MCP runs locally as a PyPI package, launched with uvx eclipse-beacon. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · eclipse-beacon
claude mcp add cyan-eclipse-technologies-llc-beacon -- uvx eclipse-beacon
What is the Eclipse Beacon MCP server?
Eclipse Beacon MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/beacon. The insurance watcher, signals your policies' expiries before they happen. It does not insure. This page covers its PyPI package (eclipse-beacon).
Is the Eclipse Beacon MCP server safe to use?
Eclipse Beacon MCP scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Eclipse Beacon MCP server expose?
Eclipse Beacon MCP exposes 5 tools: policy_ingest, policy_list, policy_get, radar_report, gap_report. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.
Is the Eclipse Beacon MCP server still maintained?
Eclipse Beacon MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Eclipse Beacon MCP server under?
Eclipse Beacon MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.