Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)
Certification scope
CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 16 pass, 1 na of 17 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/fathom.py. Run 1 PARTIAL card retained append-only (bench-suite defect); run 2 is the standing card. Non-failing bench observation: spender resolution in allowance_audit is chain-agnostic; chain-aware resolution recommended before D1 (queued as a bench note).
What it does
- Signed, versioned Protocol Registry (Uniswap/Aave/Compound/Lido across Ethereum/Arbitrum/Base): audit status as dated data with lineage, risk tiers, admin posture; addresses are never scraped live into trust and never copied from transaction history
- Position + Risk reads over a chain-transport seam: dual-source health and liquidation distance that render DIVERGENT instead of averaging when price sources disagree (bench-measured edge: 2.00% divergence still renders, 2.01% is DIVERGENT with headline fields null)
- Flagship allowance_audit: ERC-20 + Permit2 grants ranked by value at risk; unlimited grants flagged structurally; spenders Registry-resolved or labeled UNRESOLVED
- Address lookalike (poisoning) checks, depeg watch, and exposure by protocol/chain/risk tier
- D0 is reads only — no execution, draft, or signer tool exists; key-shaped input is a refused class (KEY_MATERIAL_REFUSED, incident-receipted, never echoed or stored); every output passes a lint banning advice language, yield promises, and safety claims
Tools
registry_listregistry_getregistry_verifyposition_readhealth_readdepeg_watchallowance_auditaddress_checkexposure_readreceipt_list
Problems it addresses
- My agent reads DeFi positions from one price source and calls it truth
- Somewhere in my wallets there is an unlimited token approval I forgot about, pointed at a spender I cannot name
- I copied a contract address out of my transaction history and it was not the protocol's
Not tested
- Live RPC reads — D0 ships ONLY the fixture transport behind the chain_adapter seam; no live chain was queried, and no live transport exists in this package. The seam + transport contract is the deliverable; a live transport must be implemented and benched before any read is called live.
- Seed Registry facts (contract addresses, audit firms/dates) are marked [verify] per entry for the first human release review; the release signature attests this seed file, not a completed re-audit.
- Execution, drafts, simulation, and signing (spec D1+) — no such code path exists in D0.
- Non-EVM chains and perps/bridge/vault chapters (D3) — out of D0 scope.
Bench scorecard: test-bench/results/eclipse-fathom-mcp-2026-10-25-2.json
Evaluation-intake listing
This listing records the tool's place in the Bazaar's evaluation
and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope,
and not-tested items included. It is not sold on this site, and its presence in the catalog
is not a claim beyond that evidence. The service behind every verdict is the bench:
what a bench run buys →