MCP · agent-native

Set up CapchaCloud by just asking Claude.

CapchaCloud ships a Model Context Protocol server. Connect it to Claude (or any MCP client) and your agent can provision a tenant, allow a domain, fetch keys, register webhooks, and verify or score leads — no dashboard, no copy-paste.

Connect it

Endpoint (Streamable HTTP, JSON-RPC 2.0):

https://mcp.capchacloud.com/mcp

Claude Code (one command)

claude mcp add --transport http capchacloud https://mcp.capchacloud.com/mcp

Generic MCP client (JSON)

{
  "mcpServers": {
    "capchacloud": {
      "transport": "http",
      "url": "https://mcp.capchacloud.com/mcp"
    }
  }
}

Then just ask: “Set up CapchaCloud for example.com and give me the embed.”

Tools

Provision & embed

create_tenant — mint a tenant + keys (use sandbox:true for an any-origin test key)
embed_snippet — the exact two-line embed for a key
register_webhook — add an endpoint, get the signing secret

Verify & prove

verify_lead, trust_score — lead quality
suppression_add, suppression_check — DNC list
defense_packet — court-ready memo for a record
verify_record, get_transparency — public, no PII

Transaction Evidence

Any rail — internal/other are valid, not payment-specific.

txn_seal — seal a transaction's terms + parties
txn_verify, txn_certificate — public, no PII
txn_dispute_packet — one ZIP for chargeback representment, arbitration, small claims, or a regulatory complaint. Assembles evidence only — never submits anything to a card network, Nacha, court, or regulator.

Compliance (CapchaShield)

KYC/AML checks + case management, on a separate worker.

shield_capabilities — public, what's configured right now
shield_run_check — native or a specific certified vendor
shield_case_open/note/close/get/list — CLM workflow
shield_evidence_package — the one-click evidence ZIP

Pair a check's vault_hash with txn_seal's party compliance_vault_hash to attach an independently-verified identity to a transaction.

Auth (stateless, per-tool)

create_tenant takes a provision_token argument (the platform provisioning token).
Trust tools take the tenant’s secret api_key argument.
Public tools (verify_record, get_transparency) need no secret.

Nothing sensitive is stored in the MCP server — keys are passed per call.

Full reference: /integrate.md · /openapi.json