# sh.clearhouse/clearhouse

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.8.0
- **Author:** sh.clearhouse
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.clearhouse.sh/mcp
- **Source:** https://github.com/clearhouse-sh/clearhouse-mcp
- **Endpoint health:** reachable (last checked 2026-10-16T21:43:21.044Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

**Assessment scope:** Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- **Status:** probed (endpoint answered; no code examined)
- **Scanned:** 2026-10-16T21:43:21.044Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

5 declared. Observed from a live `tools/list` probe.
- `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
- `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
- `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 sp
- `service_evidence` — Observed facts about a listing: live probe results (handshake, latency, HTTP status) and routed-call history (count, success rate, distinct callers). Includes a
- `index_stats` — How many listings Clearhouse currently indexes, broken down by source registry.

## Install

**Verdict: review** — Installable, but 3 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"clearhouse\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.clearhouse.sh/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/sh.clearhouse%2Fclearhouse
- Install plan: https://forgeregistry.com/api/v1/packages/sh.clearhouse%2Fclearhouse/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/sh.clearhouse%2Fclearhouse
- HTML page: https://forgeregistry.com/registry/sh.clearhouse%2Fclearhouse
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.