Eclipse Trust MCP
One call answers whether a bench result is real, who issued it, at what scope — and whether it is anchored on-chain, where.
status: liveclass: toolCertification & TestingAgent Governance
Vendor: Cyan Eclipse Technologies
What it does
- Answer, in one call, whether a Cyan Eclipse bench result is real: verdict byte-verbatim with scope attached, who issued it (Verity — Cyan Eclipse Technologies), and whether it is anchored on-chain, where
- Verify a Herald receipt hash end-to-end: recomputed hash match, anchor state (ANCHORED / PENDING / FAILED / NOT_ENQUEUED) with chain, transaction, and an offline-verifiable proof bundle
- Resolve ERC-8004 Validation Registry records with the verdict and its scope inside the hashed payload — testnet records labelled TESTNET, mainnet state stated typed, never implied
- Resolve an agent (ERC-8004 id, DID, or registration URL) to its registration plus a trust summary computed from the records at call time — never a stored score
- Every answer carries a verify_recipe: the server is a convenience index, never the root of trust — callers recompute from hashes and chain data themselves
Tools
trust_status · trust_verify_receipt · trust_get_bench_verdict · trust_get_validation_record · trust_resolve_agent
Platforms
- MCP over stdio
- Hosted HTTPS (streamable HTTP MCP + GET twin)
Certification
Bench verdict: PASS(local)
Certified scope: PASS(local) — Verity independent bench of v0.1.0 (2026-10-27, trust-discovery-20261027/BENCH-REPORT.md): first bench PASS-CONDITIONAL(local) with all fail-gates PASS (real Anchor batch b18e97a2 end-to-end, forged-pointer fixture, verdict fidelity, malformed battery); condition F1 (validation verify_recipe canonicalization wording) + F2/F3 closed by delta bench — final verdict PASS. Scope: stdio + HTTP twin over the bundled join index; index recomputed from sources (Bazaar verdict feed, Herald ledger, Anchor batches/proofs, ERC-8004 publisher ledger) by a fail-closed builder. Hosted PHP twin: static parity PASS at bench; execution verified by live smoke at deploy 2026-10-27.
Not tested:
- Ed25519 batch-manifest signature verification — NOT_RUN at bench (no Ed25519 verifier in the bench environment); the bundle's hash / Merkle / calldata / block-hash chain fully recomputes, and the signature is a named verify_recipe step (Anchor anchor_verify)
- Mainnet ERC-8004 validation records — none exist yet; lookups answer typed NOT_PUBLISHED_MAINNET until the publisher's separately-benched mainnet verdict-publishing activation. Testnet records resolve labelled TESTNET
- Hosted PHP twin under the local bench — no PHP runtime on the bench VM (execution NOT_RUN); static parity PASS at bench + delta, execution verified by live-endpoint smoke at deploy 2026-10-27
Live state note: Hosted twin live at https://cetech.ai/trust/mcp (+ GET twin under https://cetech.ai/trust/); official MCP Registry: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust v0.1.0 (remote entry).
Pricing
Free — read-only verification surface; no paid tier
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/trust
Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Ftrust/versions/0.1.0
Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-trust-mcp
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).