eclipse-constellation
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/constellation
What this is: eclipse-constellation is the MCP server edition
of Eclipse Constellation — Cyan Eclipse Technologies' governed,
vendor-neutral VM fleet layer for agents: one policy, one receipt
ledger, every cloud and hypervisor underneath. Policy is written by a
human, checked before anything executes, and every decision is
ledgered.
What this is not: v0.1 contains no mutation code paths at all. Nothing in this build can start, stop, resize, snapshot, or destroy a machine — lifecycle actions exist only as policy evaluations that return ALLOW/DENY with reasons.
Use
$ pip install eclipse-constellation
$ eclipse-constellation # MCP server over stdio
Or run it as a container: ghcr.io/cyan-eclipse-technologies-llc/eclipse-constellation-mcp:0.1.0.
Local stdio transport, Python stdlib only. The only target probed is the host itself, over its declared channel.
Tools (5)
| Tool | What it does |
|---|---|
target_list |
Lists declared targets only. Undeclared targets are invisible to every tool. |
policy_evaluate |
Evaluates a lifecycle action against policy — quotas, image + network allowlists, TTL + purpose discipline, snapshot-before-mutation precondition, Tier-3 approval gating. Returns ALLOW/DENY + reasons. Evaluates only; never executes. |
probe_target |
Read-only probes against a declared target via fixed command templates chosen by name (identity, uptime, disk, memory, services). No free-form command argument. |
fleet_snapshot |
Probes every declared target and stores a receipted fleet snapshot. |
receipt_list |
Lists ledger receipts (evaluations incl. DENYs, probes, snapshots) and verifies the append-only hash chain. |
Honest scope
- Observe-only in v0.1. ALLOW is a policy verdict, not an action. Execution adapters are later-phase, behind an owner gate.
- No Tier-3 ALLOW in v0.1. Destroy, network changes, and snapshot deletion require explicit human confirmation every time; the approval channel is not wired, so Tier-3 evaluations always DENY, with the reason stated.
- A policy verdict is not an endorsement and not a Bazaar listing claim.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.
Metadata
Release files for eclipse-constellation 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_constellation-0.1.0.tar.gz | 30.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_constellation-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.2 kB
Release files / eclipse_constellation-0.1.0.tar.gz
| Download URL | eclipse_constellation-0.1.0.tar.gz |
|---|---|
| Size | 30.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe28ed2637b995b59311a80fc4ca61f220381d2dda007180f72ee63302f1d69c
|
|
BLAKE2b-256 checksum How to use checksums |
7f39e8d602fff6228b937f5bab9fd73a5d204c538695372221e127d974ac9df8
|
| 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_constellation-0.1.0-py3-none-any.whl
| Download URL | eclipse_constellation-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
955412bbbe707f99d9d3863ae8e96900dcb7471767827eca68074813b4eb497f
|
|
BLAKE2b-256 checksum How to use checksums |
e528c4ea4041e17d9baf33cf9c067c20dcb61a5af9291eacdcc563bfd3360b23
|
| 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-constellation 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_constellation-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.