MCP.Market

Clearhouse MCP server

online · 100% uptime
by clearhouse.sh·sh.clearhouse/clearhouse·v0.8.0
No reviews yet

One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Clearhouse yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Clearhouse tools (5)

write = sends, deletes, buys or posts
  • call_serviceFree

    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.

  • index_statsFree

    How many listings Clearhouse currently indexes, broken down by source registry.

  • quote_callFree

    Step 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

  • search_agentsFree

    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)

  • service_evidenceFree

    Observed 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.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 818ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 42 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Clearhouse compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 78% of 4,461 AI and agents servers
Tools
5
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
196 ms
faster than 67% of 2,334 AI and agents servers

What its tools let an agent do: 5 read

Install Clearhouse in Claude Code, Cursor or VS Code

claude mcp add --transport http clearhouse https://mcp.clearhouse.sh/mcp
Add to Cursor

What the publisher says

From the Clearhouse repository's README, as published. We do not edit it. Read it on GitHub

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:

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:

  1. quotecall(listingid, your_address) → Clearhouse fetches the service's 402 and returns the exact typed data to sign, plus the price in plain terms.
  2. Your agent signs it locally.
  3. callservice(..., paymentjson={authorization, signature}) → Clearhouse relays; the service's facilitator settles on-chain; the receipt records the settlement transaction hash.

A reference client is in clients/signandcall.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

Nothing above is checked by us. What we check is on the safety report.

Clearhouse: common questions

Is Clearhouse MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Clearhouse safety report
How do I install Clearhouse?
It runs remotely at mcp.clearhouse.sh. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Clearhouse need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Clearhouse maintained?
The last commit was 62 days ago (2026-09-04). The latest release is v0.8.0.
Is Clearhouse up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Clearhouse?
Servers from other publishers that do the same job: Emilia Protocol MCP server, LLM Sandbox MCP server and Agoragentic Agent OS MCP server.
How does Clearhouse compare with other AI and agents MCP servers?
safety score 87/100 (higher than 78% of 4,461 AI and agents servers); tools 5 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Clearhouse

Same job from other publishers: the closest match first, then the best rated.

  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • LLM Sandbox
    Securely run LLM-generated code in isolated containers across 7 languages and 3 container backends.
    A
  • Agoragentic Agent OS MCP
    Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.
    B
  • Grandet
    Cheapest API for any model across official, inference and relay providers; find free credits
    A
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    More from nirholas →
    B