Assay

io.github.robertoyanguas-ops由 GitHub 帳號 robertoyanguas-ops 發布v0.4.2更新於 Oct 26, 2026

A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades.

發布方自己的服務:X402-Broker Global A2A, MCP & x402 Super-Marketplace

已驗證Streamable HTTP可網頁執行安全與監控AI 與機器學習

概覽

AI 產生的概覽

在使用前檢查遠端 MCP、A2A 與 x402 端點:存活狀態、SHA-256 工具結構固定與提示注入掃描。

可以做什麼
  • 對遠端 MCP、A2A 或 x402 端點做預檢,給出裁決,並在 tools/list 雜湊不符時拒絕
  • 探測並登錄公開 HTTPS 端點,透過 HTTP、agent-card 與 JSON-RPC 檢查建立 Observatory 檔案
  • 在付款後稽核 x402 或 A2A 服務商,取得 HMAC-SHA256 簽章的交付或 SLA 違約憑證
  • 讀取歷史一致性觀測紀錄,並在 Assay 帳本中管理固定的 SHA-256 tools/list 政策雜湊
適用情境
當助理即將呼叫或付費使用陌生的遠端代理或 MCP 端點時適用,可用於存活檢查、防止工具清單被偷換,以及留存付費服務商是否交付的簽章紀錄。
執行需求
遠端 streamable HTTP 端點;未宣告驗證、環境變數或標頭。目標必須是公開 HTTPS 來源,私有 IP 會被拒絕。
安裝前請注意
它會向你指定的第三方端點送出請求,並把觀測紀錄寫入公開帳本。與付款相關的工具需要傳入綁定 Base 或 Solana 付款的交易雜湊,只應提供你願意公開的雜湊;裁決僅供參考,並不保證端點安全。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Assay,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.robertoyanguas-ops%2Fassay/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "assay": {
      "type": "http",
      "url": "https://assay-207908449630.us-central1.run.app/mcp"
    }
  }
}

工具

4

assay_preflight

Pre-Flight MCP & A2A Security Gate

Gate a remote MCP, A2A, or x402 endpoint before calling or paying it by probing live JSON-RPC reachability, hashing tools/list (SHA-256), and scanning for prompt-injection poisoning. When expected_tools_hash is provided, any mismatch against the live tools/list digest forces verdict='deny' to block silent schema rug-pulls; when omitted, verdict reflects liveness and injection safety alone. Read-only gate; first 5 calls/IP are free and quota-exceeded calls return a 402 top-up prompt. Use before tool execution or payment; to register or refresh public leaderboard telemetry use assay_probe; to read or pin stored policy hashes use assay_get_ledger_policy; after payment use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

輸入參數target必填expected_tools_hash

assay_probe

Register & Refresh Endpoint Conformance Telemetry

Register a new remote MCP, A2A, or x402 endpoint or refresh its public Assay Observatory dossier by running a live HTTP, agent-card, and JSON-RPC tools/list inspection without policy gating. Target must be a public HTTPS origin (private IPs are rejected with a 400 error); each call appends a timestamped observation and increments rug_pulls if tools_hash drifted since the prior stored observation. Writes to the public ledger; first 5 calls/IP are free and retries are idempotent on steady schemas. Use to onboard or re-index a server; for pre-call allow/deny gating use assay_preflight; for historical observations or hash pinning use assay_get_ledger_policy; for post-payment disputes use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

輸入參數target必填

assay_verify_delivery

Verify Post-Payment x402 Delivery & Mint SLA Receipt

Audit a paid x402 or A2A provider after payment to confirm delivery or prove an SLA breach with an HMAC-SHA256 signed receipt. Passing status_code >= 500 forces verdict='sla_breach_confirmed' even if the live re-probe succeeds, while passing tx_hash cryptographically binds your Base or Solana payment signature into the receipt (omitting tx_hash still verifies liveness and issues a probe-bound receipt). Non-destructive; first 5 calls/IP are free and failed target connections do not throw tool errors. Use only after paying a provider; before payment use assay_preflight; for public indexing use assay_probe; for policy history use assay_get_ledger_policy. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

輸入參數target必填tx_hashstatus_code

assay_get_ledger_policy

Query Historical Ledger & Pin Expected Schema Hashes

Retrieve historical conformance observations and manage pinned SHA-256 tools/list policy hashes in the Assay ledger for a target endpoint. When expected_tools_hash is provided, it pins that 64-hex digest as the target's baseline policy and compares it against the latest stored observation; when omitted, it returns the stored dossier and last 20 drift observations without network probing unless the target is unindexed. Idempotent; first 5 calls/IP are free. Use to audit historical drift or pin mcp-lock.json hashes; for live pre-execution gating use assay_preflight; for live re-indexing use assay_probe; for post-payment SLA receipts use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

輸入參數target必填expected_tools_hash

版本歷史

1
  1. v0.4.2最新Oct 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。

其他 X402broker 整合