Eclipse Trust MCP

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
64%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~410Tokens (tool definitions)
~326 BTypical response size
Minimal attention impact (0.32% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "trust": {
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}

Remote endpoints

https://cetech.ai/trust/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪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.

Input Schema

{
  "type": "object",
  "properties": {},
  "required": []
}
⚪trust_verify_receipt(receipt_hash, 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.

Input Schema

{
  "type": "object",
  "properties": {
    "receipt_hash": {
      "type": "string"
    },
    "receipt": {
      "type": "object"
    }
  },
  "required": []
}
🟢trust_get_bench_verdict(product)

The current Verity bench verdict for a product, byte-verbatim with scope attached, plus the computed pointer block. No verdict returns typed NO_VERDICT.

Input Schema

{
  "type": "object",
  "properties": {
    "product": {
      "type": "string"
    }
  },
  "required": [
    "product"
  ]
}
🟢trust_get_validation_record(validation_id, request_hash, product)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "validation_id": {
      "type": "string"
    },
    "request_hash": {
      "type": "string"
    },
    "product": {
      "type": "string"
    }
  },
  "required": []
}
⚪trust_resolve_agent(agent_id, did, url, identifier)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "agent_id": {
      "type": [
        "string",
        "integer"
      ]
    },
    "did": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "identifier": {
      "type": "string"
    }
  },
  "required": []
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools