NestDaddy

Eclipse Trust MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust ยท v0.1.0

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

Connect Remote server

Terminal
claude mcp add --transport http trust https://cetech.ai/trust/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "trust": {
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "trust": {
      "type": "http",
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://cetech.ai/trust/mcp

Tools 5 found in our last check

  • 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.

Details

Endpointhttps://cetech.ai/trust/mcp (Streamable HTTP)
First published27 Oct 2026
Last updated27 Oct 2026
Registry nameio.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust

More ai and media servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.