Clearhouse MCP server

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

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 735ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 16 days ago15/15
• Maintainer identitynamespace and repository owner differ4/10

Clearhouse: common questions

Is Clearhouse MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Clearhouse safety report

How do I install Clearhouse?

It runs remotely at mcp.clearhouse.sh. Add it to Claude Code, Claude Desktop or Cursor 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 16 days ago (2026-09-04). The latest release is v0.8.0.

Is Clearhouse up?

100% of our last 5 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: Protect MCP server, Skillsmith MCP server and Ausca MCP server. Compare all Clearhouse alternatives.