Is this bench result real, who issued it, at what scope — and is it anchored on-chain, where? Eclipse Trust answers in one call, free, read-only, no key. Verdicts are issued by Verity (Cyan Eclipse Technologies) and served byte-verbatim with their scope attached. This server is a convenience index, never the root of trust: every answer carries a verify_recipe so you can recompute it from the hashes and the chain without trusting us.
POST https://cetech.ai/trust/mcp —
tools trust_status, trust_verify_receipt,
trust_get_bench_verdict, trust_get_validation_record,
trust_resolve_agent. Registry name:
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trustGET /trust/status ·
/trust/verify?receipt={hash} ·
/trust/verdict?product={id} ·
/trust/validation?id={id} ·
/trust/agent?id={did-or-agentId} ·
openapi.json/trust/proofs/{batch_id}.json —
eclipse-anchor-proof/1 bundles that verify fully offline.eclipse-trust (same tools, local sources).curl -s "https://cetech.ai/trust/verify?receipt=2127c75beb65001996231c005671f612a3ba0eb7617e0ba4063238e195e6ea19" curl -s "https://cetech.ai/trust/verdict?product=eclipse-agent-wallet-mcp"
The first is a real Herald receipt anchored on Base mainnet (batch b18e97a2…) with its Bitcoin/OpenTimestamps attestation tracked separately. Anchor state is always explicit: ANCHORED / PENDING / FAILED / NOT_ENQUEUED — never omitted, never inferred.
Powered by Cyan Eclipse Technologies LLC · cetech.ai · Eclipse Bazaar