sh.clearhousePublished by clearhouse.shOfficial publisherv0.8.0Updated Oct 24, 2026
One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts.
Clearhouse is a remote MCP server that searches a cross-registry index of 100,000+ MCP, A2A and x402 services and can route calls to them, including paid ones.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
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/sh.clearhouse%2Fclearhouse/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.Add this to your client's mcpServers config.
{
"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]
Source: README.md at commit 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)
limitqueryrequiredremote_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_idrequiredpayer_addressrequiredCall 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_idrequiredpayment_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_idrequiredHow many listings Clearhouse currently indexes, broken down by source registry.
Takes no parameters.
100% 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.
{ "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>