MCP · agent-native

Set up CapchaCloud by just asking Claude.

CapchaCloud ships a Model Context Protocol server at mcp.capchacloud.com. Connect it to Claude (or any MCP client) and your agent can mint a trust-engine tenant (cc_live_* api_key), allow a domain, register webhooks, and verify or score leads — no dashboard copy-paste. Not every dashboard feature is MCP-exposed yet (sites, SSO/SCIM, data-export remain session UI). This is CapchaCloud's product MCP — not a separate "Adam Consent-MCP" SKU, and not voice verification.

Connect the server Read the API reference
An operations specialist supervising a software workflow while a second reviewer remains available. Agent-native control
Ask, execute, verify.Use the product MCP for supported tenant, evidence, and integration actions — with capability boundaries made explicit.

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 — register HTTPS endpoint (platform-signed events)

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.

Tenant admin

  • create_tenant — mint trust-engine tenant + cc_live_* api_key (use for all trust tools)
  • create_capchaid_app — optional CapchaID-only (cid_*); not valid for trust tools
  • get_tenant, get_keys, get_entitlements — profile, keys, billing + caps
  • allow_domain, rotate_api_key, register_webhook
  • billing_checkout, billing_portal — Stripe subscription + portal URLs
  • lead_program_get, lead_program_save, lead_program_history, quick_setup — consent form + one-click setup
  • org_members_list, org_invite_*, org_member_* — team (invites require feature flag)
  • branding_get, branding_update — agency white-label (owner only; solo tenants get defaults / 403)
  • sites_list, sites_create, sites_delete — multi-site org
  • data_export — DSAR JSON (PARTIAL: schema v1 via MCP)
  • lead_notify_set, verticals_set, retention_set
  • webhook_deliveries_list, webhook_replay — delivery log + re-queue
  • security_audit_list, audit_chain_verify
  • organizations_list, onboarding_preflight
  • sso_get, sso_put — PARTIAL: SAML not live on trust-engine
  • scim_token_status, scim_token_rotate
  • auth_domains_list, auth_domains_create — 503 if CF SaaS unset

CapchaWallet

  • wallet_start — email consumer magic link
  • wallet_list, wallet_revoke, wallet_export — token from link

ISO 20022 evidence

  • iso20022_seal, iso20022_seal_batch — seal message XML
  • iso20022_records, iso20022_corroborate — list + bank status reports
  • iso20022_verify, iso20022_certificate — public, no PII

Compliance (CapchaShield)

KYC/AML checks + case management, on a separate worker. Certified-vendor adapters are scaffolded — each activates when you supply BYO credentials (shield_capabilities shows live status).

  • shield_capabilities — public, what's configured right now
  • shield_run_check — native or a specific certified vendor (no silent downgrade)
  • 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.

Compliance Oracle & RSN

Advisory only — never executes, blocks, or reverses funds. RSN bundles compose existing evidence; they confer no regulatory approval or settlement finality.

  • oracle_authorize — sealed allow/deny/review decision (advisory)
  • oracle_rules — public rule kernel listing
  • rsn_profile — compose reserve + settlement + oracle evidence
  • rsn_verify — public handle resolution

Auth (stateless, per-tool)

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

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