Eclipse Sunset
MCP deprecation radar: detects deprecated/removed tools and versions from witnessed, hash-chained registry snapshots and generates a migration diff for an agent's config.
status: in-developmentclass: mcpAgent InfrastructureTrust & Receipts
Vendor: Cyan Eclipse Technologies
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
ingest_snapshot · detect_sunsets · migration_diff · verify_sunset_claim · chain_status
Platforms
- MCP over stdio
Certification
Bench verdict: CERTIFIED (local, fixture)
Certified scope: CERTIFIED (local, fixture) — Verity independent bench 2026-10-26, REBENCH-1 of the v0.1.1 D1 fix (repo @ 88f2aa6): probe 5 chain attacks PASS 4/4 + strict extras 9/9 — on a tampered ledger the previously-PROVEN claim returns UNPROVEN + chain_invalid: true, no forged PROVEN is minted, detect_sunsets / migration_diff / ingest_snapshot refuse CHAIN_INVALID; full prior suite re-run 44/44 (unwitnessed claims UNPROVEN, witnessed proof citing bench-recomputed snapshot hashes, fixture-pair detection exact, migration diff sane, hygiene 14/14). Prior verdict on v0.1.0 (VERDICT.md): CONDITIONAL (local, fixture), 41/44, defect D1 HIGH — closed by this re-bench. Scope = LOCAL/fixture only: local JSON snapshot ingest, stdio transport, bundled weather fixtures. No live-registry claim is made or tested — none exists in v0.1.1, and the server honestly says so.
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
Live state note: Bench evidence: argus-batch-20261026/bench/sunset/VERDICT.md + REBENCH-1.md (Verity, independent bench over stdio JSON-RPC). This bench issued no test-bench/results scorecard; scorecard_ref is null and no scorecard is claimed or hosted for this product.
Pricing
FREE — free local v0.1.1, open reference implementation; funnel role: the free radar feeds paid listing-hygiene and re-bench work. No payment anything in this server.
Install / verify
No install command is published for this product in the catalog or its registry record.
Official MCP Registry name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-sunset-mcp
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Feclipse-sunset-mcp/versions/0.1.1
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-sunset-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).