clearhouse

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

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
96%
Vollständigkeit des Schemas
66%
Qualität der Benennung
88%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,010Tokens (Tool-Definitionen)
~1.2 KBTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.79% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

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

Remote-Endpunkte

https://mcp.clearhouse.sh/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (5)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢search_agents(query, remote_only, limit)

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)

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "query": {
      "title": "Query",
      "type": "string"
    },
    "remote_only": {
      "default": false,
      "title": "Remote Only",
      "type": "boolean"
    },
    "limit": {
      "default": 10,
      "title": "Limit",
      "type": "integer"
    }
  },
  "required": [
    "query"
  ],
  "title": "search_agentsArguments"
}

Ausgabe-Schema

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "search_agentsOutput"
}
🟢quote_call(listing_id, payer_address, args_json)

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

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "listing_id": {
      "title": "Listing Id",
      "type": "integer"
    },
    "payer_address": {
      "title": "Payer Address",
      "type": "string"
    },
    "args_json": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "additionalProperties": true,
          "type": "object"
        }
      ],
      "default": "{}",
      "title": "Args Json"
    }
  },
  "required": [
    "listing_id",
    "payer_address"
  ],
  "title": "quote_callArguments"
}

Ausgabe-Schema

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "quote_callOutput"
}
🟢call_service(listing_id, tool, args_json, caller_ref, payment_json)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "listing_id": {
      "title": "Listing Id",
      "type": "integer"
    },
    "tool": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Tool"
    },
    "args_json": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "additionalProperties": true,
          "type": "object"
        }
      ],
      "default": "{}",
      "title": "Args Json"
    },
    "caller_ref": {
      "default": "mcp-client",
      "title": "Caller Ref",
      "type": "string"
    },
    "payment_json": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "additionalProperties": true,
          "type": "object"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Payment Json"
    }
  },
  "required": [
    "listing_id"
  ],
  "title": "call_serviceArguments"
}

Ausgabe-Schema

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "call_serviceOutput"
}
⚪service_evidence(listing_id)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "listing_id": {
      "title": "Listing Id",
      "type": "integer"
    }
  },
  "required": [
    "listing_id"
  ],
  "title": "service_evidenceArguments"
}

Ausgabe-Schema

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "service_evidenceOutput"
}
⚪index_stats

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

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "title": "index_statsArguments"
}

Ausgabe-Schema

{
  "type": "object",
  "properties": {
    "result": {
      "title": "Result",
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "title": "index_statsOutput"
}

Empfohlene Prompts

search_research
Search for information about [topic] using clearhouse
Erwartete Tools: search_agents
find_specific
Find [specific item] using clearhouse
Erwartete Tools: search_agents

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet5 Tools
verifiziertVersion nicht aufgezeichnet5 Tools