Eclipse Sunset
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Eclipse Sunsetingest fixtures/weather-v2.json, then generate a migration diff for fixtures/agent-config.json"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Eclipse Sunset
MCP deprecation radar — detects deprecated/removed tools and versions from witnessed registry snapshots and generates a migration diff for an agent's config.
Scope label: LOCAL / fixture. v0.1 ingests local registry snapshot JSON files only. It does not crawl live registries. Live crawling is a later phase.
Status: v0.1.1 — CERTIFIED (local, fixture) (Verity re-bench,
2026-10-26: probe 5 chain-attack suite 4/4 + strict extras 9/9, full
prior suite 44/44; D1 closed). Spec: SPEC.md.
Novel mechanism
Sunset notices are witnessed against registry history, so a "deprecated" claim is provable — and the migration diff is generated from the witnessed before/after schemas, not scraped docs.
Each ingested snapshot is SHA-256 hashed over its canonical JSON and
hash-chained in ingest order (chain_hash = sha256(prev_hash + snapshot_hash)). Findings cite both snapshot hashes of the witnessed
pair. A claim with no witnessed pair behind it returns UNPROVEN.
Related MCP server: dsh-schema-migration-proof
Tools (exactly 5)
Tool | What it does |
| Validate a snapshot ( |
| Between two witnessed snapshots of the same server: tools removed, tools newly deprecated, version changes, schema-breaking changes — each finding cites both snapshot hashes. |
| Given a server + an agent config listing tools used, produce the diff: which used tools are sunset in the newer witnessed snapshot and what changed in their schemas. |
| Claim "tool X deprecated/removed" → |
| Verify hash-chain integrity (recomputes every hash + link; tamper → |
Fixtures
fixtures/weather-v1.json and fixtures/weather-v2.json: the same
fixture server at v1.0.0 / v2.0.0 — one tool removed (legacy_lookup),
one deprecated (get_alerts), one schema-breaking change
(get_forecast gains required units), one unchanged
(convert_units). fixtures/agent-config.json is a sample agent
config for migration_diff.
Pricing
FREE + funnel role — free radar feeds paid listing-hygiene and re-bench work. No payment anything in this server.
Run
python3 server.py # MCP over stdio JSON-RPC
python3 -m unittest discover -s tests -vState (the witnessed chain ledger) lives in data/ or the directory
named by SUNSET_DATA_DIR.
Python 3, standard library only.
MIT License · Copyright © 2026 Cyan Eclipse Technologies LLC · cetech.ai
This server cannot be deployed
Maintenance
Related MCP Connectors
Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.
A read-only verified record of agent-operable GTM tools: search, fetch, compare, track changes.
Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.
Snapshot and restore service for agent state and DID-bound configuration
Related MCP Servers
- AlicenseCqualityCmaintenanceEnables coding agents to query, compare, and audit local profiler traces, benchmarks, memory captures, and execution evidence without uploading code or data, using CLI and MCP interfaces.111132 PyPI220MIT
- AlicenseNot gradedqualityCmaintenanceLets users inspect and verify content-addressed schema migration evidence offline, checking idempotence, reversible rollback, required invariants, and explicit lossy-field disclosure without executing migrations or accessing data.MIT
- AlicenseNot gradedqualityBmaintenanceEnables deterministic analysis of a single Agent tool-catalog snapshot and comparison of two snapshots through read-only JSON-RPC tools, reporting digests, schema statistics, duplicates, collisions, budget checks, and diffs.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables recording agent proposals, executions, redactions and annotations into an append-only, hash-linked evidence chain, then exporting a self-contained range and verifying offline from the export's own bytes alone so a third party can check history without trusting the agent runtime or its storage.MIT