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.
无需输入参数。

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC由 GitHub 账号 CYAN-ECLIPSE-TECHNOLOGIES-LLC 发布v0.1.0更新于 Oct 29, 2026
Is this bench result real? Who issued it, at what scope, anchored where? One call answers.
远程 MCP 服务器,用于核验 AI 基准评测结论、Herald 收据与 ERC-8004 验证记录的真实性、来源与链上锚定状态。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC%2Ftrust/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"eclipse-trust": {
"type": "http",
"url": "https://cetech.ai/trust/mcp"
}
}
}该仓库没有 README。
Server health + data provenance: index build time, source recompute checks, verdict/receipt/anchor counts, mainnet vs testnet posture. Call this first to judge freshness.
无需输入参数。
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.
receiptreceipt_hashThe current Verity bench verdict for a product, byte-verbatim with scope attached, plus the computed pointer block. No verdict returns typed NO_VERDICT.
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.
productrequest_hashvalidation_idResolve an agent by ERC-8004 agent_id, DID, or registration URL: registration summary plus a trust summary computed from the records at call time.
didurlagent_ididentifier已满足适用检查项的 75%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。
请在仓库或注册中心条目中声明许可证。