Cyan Eclipse Sunset

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio

What it does

• Novel mechanism — sunset claims witnessed against registry history: a "deprecated" or "removed" claim is PROVEN only when a witnessed snapshot pair supports it; the migration diff is generated from the witnessed before/after schemas, never scraped docs. A claim with no witnessed pair behind it returns UNPROVEN — there is no announcement input surface at all, and the bench's plausible announced claims (with evidence text supplied) all returned UNPROVEN.
• Every ingested snapshot is SHA-256 hashed over its canonical JSON and hash-chained in ingest order (chain_hash = sha256(prev_hash + snapshot_hash)); every finding cites both snapshot hashes of the witnessed pair, recomputed independently at bench and matched exactly (from 7ebb2386…411f5 / to cd563c11…5c4ab on the bundled weather fixtures).
• Detection over a witnessed pair: tools removed, tools newly deprecated, version changes, and schema-breaking changes (property removed / property type changed / required added) — bench-exact on the fixture pair: 1 removed (legacy_lookup), 1 newly deprecated (get_alerts), 1 schema-breaking (get_forecast, required_added: units), version 1.0.0→2.0.0; the unchanged tool (convert_units) appears nowhere in findings.
• Tamper gate (bench defect D1, fixed v0.1.1, re-benched): every proof-issuing surface is gated on full chain verification — verify_sunset_claim returns UNPROVEN + chain_invalid on a tampered ledger, and detect_sunsets / migration_diff / ingest_snapshot refuse with CHAIN_INVALID; a one-bool edit to the ledger mints no PROVEN and no findings.
• Migration diff for an agent's config: per used tool — removed / deprecated / schema_breaking (with witnessed schema-change detail) / unchanged / not_in_witnessed_snapshots, generated from witnessed before/after schemas only.
• Honest scope: LOCAL / fixture in v0.1.1 — ingests local registry snapshot JSON files only; it does not crawl live registries, fetch any URL, or scrape documentation. Python 3 standard library only; no network code exists in the package; no payment anything, no accounts, keys, credentials, or checkout.

Tools

Problems it addresses

• A registry announcement says a tool my agent depends on is deprecated — I need that claim proven against witnessed registry history, not trusted from the announcement
• When a server ships a new version, I need to know exactly which tools in my agent's config were removed, deprecated, or schema-broken — as a diff generated from the witnessed before/after schemas
• If the snapshot ledger itself was tampered with, I need every proof surface to refuse or flag it — never mint claims from forged data

Not tested

• Live registry crawling — not in v0.1.1 by design (later phase); the server ingests local snapshot JSON files only and makes no live-registry claim
• Hosted or remote serving — v0.1.1 is local stdio only
• A schema_breaking claim type in verify_sunset_claim — by SPEC design the claim enum is deprecated|removed only; the schema-breaking proof surface is detect_sunsets / migration_diff, verified there at bench