# sh.clearhouse/clearhouse (remote · mcp.clearhouse.sh)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `mcp.clearhouse.sh`: 73/100 (this document), [markdown](https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp.md), [page](https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp)

## Channel facts

- Endpoint: `https://mcp.clearhouse.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 621 tokens (~124/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the sh.clearhouse/clearhouse MCP server?

sh.clearhouse/clearhouse is a hosted endpoint at https://mcp.clearhouse.sh/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "sh-clearhouse-clearhouse": {
      "type": "http",
      "url": "https://mcp.clearhouse.sh/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sh-clearhouse-clearhouse]
url = "https://mcp.clearhouse.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-clearhouse-clearhouse": {
      "type": "remote",
      "url": "https://mcp.clearhouse.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sh-clearhouse-clearhouse --url 'https://mcp.clearhouse.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sh-clearhouse-clearhouse:
    url: "https://mcp.clearhouse.sh/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sh-clearhouse-clearhouse": {
      "Transport": "http",
      "Url": "https://mcp.clearhouse.sh/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sh-clearhouse-clearhouse -t streamable-http -u 'https://mcp.clearhouse.sh/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `search_agents` (~88 tokens)

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)

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `remote_only` (boolean)

Output parameters:

- `result` (string)

### `quote_call` (~141 tokens)

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

Input parameters:

- `args_json`
- `listing_id` (integer, required)
- `payer_address` (string, required)

Output parameters:

- `result` (string)

### `call_service` (~219 tokens)

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.

Input parameters:

- `args_json`
- `caller_ref` (string)
- `listing_id` (integer, required)
- `payment_json`
- `tool`

Output parameters:

- `result` (string)

### `service_evidence` (~98 tokens)

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.

Input parameters:

- `listing_id` (integer, required)

Output parameters:

- `result` (string)

### `index_stats` (~22 tokens)

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

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 72
- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 71
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 69
- 2026-09-18: 69
- 2026-09-17: 68
- 2026-09-16: 68
- 2026-09-15: 67
- 2026-09-14: 67
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 65
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 63
- 2026-09-05: 63
- 2026-09-04: 62

## Common questions

### What is the sh.clearhouse/clearhouse MCP server?

sh.clearhouse/clearhouse is an MCP server listed in the public MCP registry as sh.clearhouse/clearhouse. One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts. This page covers its hosted endpoint (https://mcp.clearhouse.sh/mcp).

### Is the sh.clearhouse/clearhouse MCP server safe to use?

sh.clearhouse/clearhouse scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the sh.clearhouse/clearhouse MCP server expose?

sh.clearhouse/clearhouse exposes 5 tools: search_agents, quote_call, call_service, service_evidence, index_stats. Their descriptions and schemas cost roughly 568 tokens of context every time the server is loaded.

### Does the sh.clearhouse/clearhouse MCP server require authentication?

No. We connected to sh.clearhouse/clearhouse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the sh.clearhouse/clearhouse MCP server still maintained?

sh.clearhouse/clearhouse is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.clearhouse.sh/mcp
- Repository: https://github.com/clearhouse-sh/clearhouse-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp.json
- HTML version of this page: https://verifymcp.io/servers/sh-clearhouse-clearhouse/mcp