io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust · v0.1.0 · agents-and-memory
Eclipse Trust MCP is healthy: it completed an MCP handshake in 985 ms and exposes 5 tools.
Is this bench result real? Who issued it, at what scope, anchored where? One call answers.
Endpoint: https://cetech.ai/trust/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 985 ms |
| Last checked (UTC) | 2026-10-27T18:20:23.429Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-27T18:20:23.429Z | Healthy | 985 |
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. |