Eclipse Cluster MCP
Signed images, governed runtimes — the gate runs first: no verified signature and provenance, no workload.
status: in-developmentclass: mcpContainer Security
Vendor: Cyan Eclipse Technologies
What it does
- Resolve an image's digest from its registry with a read-only OCI client (digest computed over served bytes)
- Verify cosign-style signatures (ECDSA P-256, Ed25519, RSA) with a pure-stdlib gate
- Verify DSSE / in-toto provenance against a written policy and local trust bundle
- Per-check PASS/FAIL verdict (10 gate checks), fail-closed on every error
- Wrong-signer failures distinguished: forgery fails the signature, an unauthorized signer fails policy
Tools
verify_image · policy_show · receipt_list
Platforms
- MCP over stdio
Certification
Bench verdict: CERTIFIED(simulator)
Certified scope: CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 18/19 checks pass, 1 na (U1 auth: stdio process boundary). Simulator scope: local stub registry, openssl-signed fixtures. Run by W-003 (Verity), suites/cluster.py.
Not tested:
- Runtime/orchestration phases K1-K3 not built — v0.1 is the K0 verification gate only
- Keyless/Fulcio certificate signatures not accepted by design in v0.1 (key-based trust bundles only)
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-cluster-mcp-2026-10-25.json
Pricing
Free / open reference implementation
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-cluster-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).