Skip to content
Clearhouse logo

Clearhouse MCP server

Which MCP servers are Clearhouse's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Clearhouse

Whose server it is
  • Registry namesh.clearhouse/clearhouseverified in the MCP registry

The registry name sits under clearhouse.sh. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools5
  • Server calls itselfclearhouse
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 275 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: search MCP servers and agents across public registries; route calls to MCP, A2A or HTTP endpoints.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "search MCP servers and agents across public registries", the likely first call is search_agents.
  • For "route calls to MCP, A2A or HTTP endpoints", the likely first call is call_service.
  • Parameters are untyped or undescribed in 4 of 5 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer234 ms
  • Space in an agent's context≈ 935 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsC · 70 of 100
  • Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 5
  • Not saying whether it only reads or can destroy: 5 of 5

What an agent can do with it

  • can do · search MCP servers and agents across public registries
  • can do · route calls to MCP, A2A or HTTP endpoints
  • not sure · verify signed receipts for service calls

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-26
  • search_agents

    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)

  • quote_call

    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…

  • call_service

    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…

  • service_evidence

    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…

  • index_stats

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.clearhouse.sh/mcp as a custom connector in the settings.

OpenAPI spec

7 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.