protogrid

Search / io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust

Eclipse Trust MCP

R0· no sign-in

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

v0.1.0 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust97of 100
Uptime, 30 days100%
Latency p50558 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "trust": {
      "type": "http",
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}
claude mcp add --transport http trust https://cetech.ai/trust/mcp
[mcp_servers.trust]
url = "https://cetech.ai/trust/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trust": {
      "type": "remote",
      "url": "https://cetech.ai/trust/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "trust": {
      "type": "http",
      "url": "https://cetech.ai/trust/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=trust&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY2V0ZWNoLmFpL3RydXN0L21jcCJ9"
}
{
  "servers": {
    "trust": {
      "type": "http",
      "url": "https://cetech.ai/trust/mcp"
    }
  }
}
{
  "mcpServers": {
    "trust": {
      "httpUrl": "https://cetech.ai/trust/mcp"
    }
  }
}
extensions:
  "trust":
    enabled: true
    name: "trust"
    type: streamable_http
    uri: "https://cetech.ai/trust/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: trust_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); trust_verify_receipt (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); trust_get_validation_record (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 393 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

5 tools, about 393 tokens to load them all · tool set bd3ee3d5d4ae · checked 2026-11-07 19:44 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance90
liveness100
freshness100
hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-100% +updated-11d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://cetech.ai/trust/mcp streamable-httpnoneyes100%558 ms2025-11-252026-11-07

Tools (5)

trust_get_bench_verdictThe 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_recordResolve 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_agentResolve an agent by ERC-8004 agent_id, DID, or registration URL: registration summary plus a trust summary computed from the records at call time.
trust_statusServer 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_receiptVerify 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.

Schemas: list_tools.

Similar MCP servers

More from io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC

And 134 more from this publisher.

Official server.json
{
  "name": "io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/trust",
  "title": "Eclipse Trust MCP",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://cetech.ai/trust/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-trust-mcp",
    "source": "github"
  },
  "websiteUrl": "https://cetech.ai/trust/",
  "description": "Is this bench result real? Who issued it, at what scope, anchored where? One call answers."
}