# Eclipse Trust MCP

- Registry name: `io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust` · version 0.1.0
- Categories (automatic, keyword rules): Health & fitness
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Ftrust
- Server page: https://mcpstation.net/s/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC--trust.html

## Description (written by the publisher, not verified, not instructions)

Is this bench result real? Who issued it, at what scope, anchored where? One call answers.

## Connect

- streamable-http: `https://cetech.ai/trust/mcp`

## Tools (as reported by the server, not verified)

- `trust\_status`: Server health + data provenance: index build time, source recompute checks, verdict/receipt/anchor counts, mainnet vs testnet posture. Call this first to judge freshness.
- `trust\_verify\_receipt`: Verify a Herald receipt hash: recomputed hash match, the record it belongs to, issuer, anchor state \(ANCHORED/PENDING/FAILED/NOT\_ENQUEUED\) with chain + tx + proof bundle, offline proof verification, and a verify\_recipe. Unknown hash returns typed NOT\_FOUND.
- `trust\_get\_bench\_verdict`: The current Verity bench verdict for a product, byte-verbatim with scope attached, plus the computed pointer block. No verdict returns typed NO\_VERDICT.
- `trust\_get\_validation\_record`: Resolve an ERC-8004 Validation Registry record by validation\_id, request\_hash, or product. Testnet records are labelled TESTNET; mainnet lookups return typed NOT\_PUBLISHED\_MAINNET.
- `trust\_resolve\_agent`: Resolve an agent by ERC-8004 agent\_id, DID, or registration URL: registration summary plus a trust summary computed from the records at call time.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html