sh.clearhouse/clearhouse
REMOTE · MCP.CLEARHOUSE.SH · SCANNED SEP 27
One search across every agent registry: 100K+ MCP/A2A/x402 services, signed receipts.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.clearhouse.sh
claude mcp add --transport http sh-clearhouse-clearhouse 'https://mcp.clearhouse.sh/mcp'
{
"mcpServers": {
"sh-clearhouse-clearhouse": {
"url": "https://mcp.clearhouse.sh/mcp"
}
}
} {
"servers": {
"sh-clearhouse-clearhouse": {
"type": "http",
"url": "https://mcp.clearhouse.sh/mcp"
}
}
} [mcp_servers.sh-clearhouse-clearhouse] url = "https://mcp.clearhouse.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-clearhouse-clearhouse": {
"type": "remote",
"url": "https://mcp.clearhouse.sh/mcp",
"enabled": true
}
}
} openclaw mcp add sh-clearhouse-clearhouse --url 'https://mcp.clearhouse.sh/mcp' --transport streamable-http
mcp_servers:
sh-clearhouse-clearhouse:
url: "https://mcp.clearhouse.sh/mcp" {
"McpServers": {
"sh-clearhouse-clearhouse": {
"Transport": "http",
"Url": "https://mcp.clearhouse.sh/mcp"
}
}
} assistant mcp add sh-clearhouse-clearhouse -t streamable-http -u 'https://mcp.clearhouse.sh/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://mcp.clearhouse.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.clearhouse.sh | CN=YE1,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 54dab254243b7f376ecf56be80d591c4059 |
| SANs: mcp.clearhouse.sh | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.clearhouse.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| clearhouse.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.clearhouse.sh/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.clearhouse.sh/mcp | HTTPS enforced | 308 | https://mcp.clearhouse.sh/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_service ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| args_json | – | – | – |
| caller_ref | string | – | – |
| listing_id | integer | yes | – |
| payment_json | – | – | – |
| tool | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
index_stats ~22
How many listings Clearhouse currently indexes, broken down by source registry.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
quote_call ~141
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
| Name | Type | Req | Description |
|---|---|---|---|
| args_json | – | – | – |
| listing_id | integer | yes | – |
| payer_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_agents ~88
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)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| remote_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
service_evidence ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.