Eclipse Trust MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Remote MCP server for checking the authenticity of AI bench verdicts, Herald receipts and ERC-8004 validation records, with provenance and anchor state.

What you can do
  • Check server health and data provenance, including index build time, source recompute checks and mainnet versus testnet posture.
  • Verify a Herald receipt hash: recomputed hash match, issuer, anchor state with chain, transaction and proof bundle, plus offline proof verification.
  • Fetch the current Verity bench verdict for a product, byte-verbatim with scope and a computed pointer block.
  • Resolve ERC-8004 Validation Registry records by validation_id, request_hash or product, with testnet records labelled.
  • Resolve an agent by ERC-8004 agent_id, DID or registration URL and get a trust summary computed at call time.
When to use it
Use it when you need to confirm that a bench result or validation record is genuine, see who issued it and at what scope, and check whether it is anchored on-chain. Useful for auditing AI product claims or agent registrations before relying on them.
Requirements
A remote streamable HTTP endpoint at cetech.ai; no package, environment variables or headers are declared. Network access to that endpoint is required.
Before you install
No authentication is declared, so treat results as public lookups only. Mainnet records may be absent: lookups can return NOT_PUBLISHED_MAINNET, and testnet records are labelled TESTNET. Unknown hashes and missing verdicts return typed NOT_FOUND or NO_VERDICT rather than errors.

Installation

In SourceWeft

  1. Open Eclipse Trust MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Ftrust/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "eclipse-trust": {
      "type": "http",
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}

README

This repository has no README.

Tools

5

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.

Takes no parameters.

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.

Parametersreceiptreceipt_hash

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.

Parametersproductrequired

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.

Parametersproductrequest_hashvalidation_id

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.

Parametersdidurlagent_ididentifier

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.