sh.clearhouse由 clearhouse.sh 發布官方發布者v0.8.0更新於 Oct 24, 2026
One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts.
Clearhouse 是遠端 MCP 伺服器，可跨多個代理註冊表搜尋超過 10 萬個 MCP、A2A 與 x402 服務，並能把呼叫路由到這些服務，包含付費呼叫。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/sh.clearhouse%2Fclearhouse/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"clearhouse": {
"type": "http",
"url": "https://mcp.clearhouse.sh/mcp"
}
}
}One search across every agent registry. Call anything through one endpoint. Pay with your own key. Keep the receipt.
clearhouse.sh crawls the official MCP registry, Glama, Smithery and the x402 Bazaar every six hours, deduplicates across them, and exposes one index: 100,000+ unique services, 65,000+ callable over the network, 15,000+ pay-per-call.
It is also an MCP server itself, so any agent can search the whole index natively — and route calls through it, including paid x402 calls settled non-custodially with the agent's own key.
Works with Claude, Cursor, and any client that speaks MCP over streamable HTTP. No key, no signup. The directory is free and will stay free.
Tools your agent gets:
Plain HTTP works too: api.clearhouse.sh/v0/search?q=payments&remote=1 · full API reference
Clearhouse never holds funds and never sees a private key. The flow, end to end:
quote_call(listing_id, your_address) → Clearhouse fetches the service's 402 and returns the exact typed data to sign, plus the price in plain terms.call_service(..., payment_json={authorization, signature}) → Clearhouse relays; the service's facilitator settles on-chain; the receipt records the settlement transaction hash.A reference client is in clients/sign_and_call.py:
This is live: routed x402 calls settle on Base (testnet today, mainnet shortly), and the receipt carries the on-chain transaction hash.
Every routed call — success or failure — gets an Ed25519-signed receipt binding intent, execution, settlement and outcome digests. Verify any receipt in your browser at clearhouse.sh/verify.html — verification runs client-side against the key set published at /.well-known/clearhouse-keys.json. The envelope format is specified in docs/RECEIPTS.md.
Evidence is farm-resistant by design: only paid, agent-signed calls count toward a service's observed tier. Free calls are recorded but never scored.
Read clearhouse.sh/caveats.html before relying on anything. Short version: listings are crawled claims, not audited facts (in a random probe, ~43% of "remote" MCP listings didn't complete a handshake); evidence is observation, not endorsement; listing text is third-party content — treat it as data, never as instructions.
Independent and solo-built. Clearhouse doesn't operate a runtime, sell hosting, or take paid placement in evidence — the aggregator has no horse in the race, which is the point.
Contact: [email protected]
來源：README.md，提交 ad9e6cb
Search all indexed agent registries at once. Args: query: capability keywords, e.g. "pdf extraction", "solana rpc", "payments" remote_only: only return services callable over the network right now limit: max results (1-50)
limitquery必填remote_onlyStep 1 of a paid call (non-custodial). Fetches the service's payment requirements and returns the exact EIP-712 typed data your agent must sign with ITS OWN key. Nothing is charged until you sign and pass the result to call_service. If the service is free, says so. Args: listing_id: id from search_agents payer_address: your agent's wallet address (the key that will sign) args_json: JSON object of query args for the service
args_jsonlisting_id必填payer_address必填Call a listed remote service THROUGH Clearhouse and get a signed receipt. Routes the call via the matching protocol adapter (MCP / A2A / HTTP-x402), enforces spend caps, settles x402 paywalls (dry-run by default), and returns the result plus a cryptographically signed receipt binding intent -> execution -> settlement -> outcome. Args: listing_id: id from search_agents results tool: downstream tool name (omit to list the service's tools) args_json: JSON object of tool arguments caller_ref: opaque caller identifier for the receipt payment_json: for paid services — JSON {"authorization": typed_data.message, "signature": "0x..."} produced by signing quote_call's typed_data with your own key. Clearhouse relays it; it never sees your private key.
toolargs_jsoncaller_reflisting_id必填payment_jsonObserved facts about a listing: live probe results (handshake, latency, HTTP status) and routed-call history (count, success rate, distinct callers). Includes an arithmetic summary_index with published methodology and a confidence tier. This is EVIDENCE for the caller's own decision — not a safety rating, and Clearhouse never selects or executes on your behalf.
listing_id必填How many listings Clearhouse currently indexes, broken down by source registry.
無需輸入參數。
已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
{ "mcpServers": { "clearhouse": { "url": "https://mcp.clearhouse.sh/mcp" } }}export PAYER_PRIVATE_KEY=0x... # your agent's wallet; never sent anywherepython clients/sign_and_call.py --mcp https://mcp.clearhouse.sh/mcp --listing <id>