Clearhouse

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.

Add it to your agent (30 seconds)

{
  "mcpServers": {
    "clearhouse": {
      "url": "https://mcp.clearhouse.sh/mcp"
    }
  }
}

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:

Tool	What it does
`search_agents`	Full-text search across every indexed registry, duplicates collapsed
`service_evidence`	What Clearhouse has observed about a service: live handshake, latency, paid routed-call history, summary index with published methodology
`quote_call`	For paid services: returns the exact EIP-712 payload your agent signs with its own key
`call_service`	Routes the call (MCP / A2A / HTTP-x402) and returns the result plus a signed receipt
`index_stats`	What's in the index right now

Plain HTTP works too: api.clearhouse.sh/v0/search?q=payments&remote=1 · full API reference

Paying for services, non-custodially

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.
Your agent signs it locally.
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:

export PAYER_PRIVATE_KEY=0x...   # your agent's wallet; never sent anywhere
python clients/sign_and_call.py --mcp https://mcp.clearhouse.sh/mcp --listing <id>

This is live: routed x402 calls settle on Base (testnet today, mainnet shortly), and the receipt carries the on-chain transaction hash.

Receipts

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.

What it does not do

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.

About

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: contact@clearhouse.sh

clearhouse mcp