Skip to content

clearhouse MCP server

sh.clearhouse/clearhouseclearhouse.shstreamable-httpv0.8.0Scanned

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

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the clearhouse MCP server can do

The clearhouse MCP server is published by clearhouse.sh, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: quote_call, call_service, service_evidence and index_stats), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.8.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 4Claude Code: ask
  • call_serviceCall a listed remote service THROUGH Clearhouse and get a signed receipt.No findings

    Why it is in this group

    • The name "call_service" says "call": a word for a change.
    Description, as the server wrote it
    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_statsHow many listings Clearhouse currently indexes, broken down by source registry.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How many listings Clearhouse currently indexes, broken down by source registry.
  • quote_callStep 1 of a paid call (non-custodial).No findings

    Why it is in this group

    • The name "quote_call" says "call": a word for a change.
    Description, as the server wrote it
    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
  • service_evidenceObserved facts about a listing: live probe results (handshake, latency, HTTP status) and routed-call history (count, success rate, distinct callers).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • search_agentsSearch all indexed agent registries at once.No findings

    Why it is in this group

    • The name "search_agents" says "search": a word for reading.
    Description, as the server wrote it
    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)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.clearhouse.sh/mcp: tools/list returned 5 tools to an anonymous client, including quote_call (write), call_service (write), service_evidence (write), index_stats (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.8.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__clearhouse__search_agents"
    ],
    "ask": [
      "mcp__clearhouse__quote_call",
      "mcp__clearhouse__call_service",
      "mcp__clearhouse__service_evidence",
      "mcp__clearhouse__index_stats"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as clearhouse. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/sh.clearhouse/clearhouse/verify?hash=737e1d264a890a21db215b8a25c3a3d6ae9005a492471260de605e5f92cd4a70" | jq -e '.changed == false'

Pinned hash 737e1d264a89, from Nov 18, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/sh.clearhouse/clearhouse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for sh.clearhouse/clearhouse
[![Anlyon Radar](https://radar.anlyon.com/badge/sh.clearhouse/clearhouse.svg)](https://radar.anlyon.com/servers/sh.clearhouse/clearhouse)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

clearhouse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the clearhouse MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the clearhouse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the clearhouse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the clearhouse MCP server have?

5 tools: 4 write, 1 read. quote_call, call_service, service_evidence, index_stats and search_agents.

Does the clearhouse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the clearhouse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the clearhouse MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.