Agents Index

Proof Holdings

Online

One API, all things verified — control, delegation, human approval, anti-impersonation.

Visit publisherConnectJSON

What it can do: 80 tools

  • create_verificationCreate a new identity verification. Initiates a verification flow for an asset identifier (phone number, email, domain, social handle, wallet address, account, or Telegram bot). Agent usage: pass the asset `type`, the d
  • get_verification read-onlyGet a verification by ID. Returns the full verification object including status, channel, and proof token if verified. Before calling this for a challenge you created, make sure your reply text already shows the user wh
  • list_verifications read-onlyList verifications with optional filters. Returns paginated results. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this
  • trigger_verificationTrigger a DNS/HTTP verification check for a pending domain verification. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open t
  • submit_verification_codeSubmit an OTP/challenge code for a pending verification. Accepted ONLY where we delivered the code out-of-band to the party being verified: type "email", and type "domain" with channel "email". Any other pair answers 400
  • resend_verificationResend a verification message (email channel only). Generates and sends a new code. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does
  • test_verifyAuto-complete a verification in test mode (pk_test_* API keys only). Useful for testing flows without real OTP delivery. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then c
  • list_verified_users read-onlyList verified users grouped by external_user_id. Shows all verifications per user. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does
  • get_verified_user read-onlyGet a single verified user and their verifications by external user ID. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open th
  • start_domain_verificationStart a B2B domain verification. Creates a verification record and returns DNS/HTTP instructions for the customer to complete. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate),
  • check_domain_verificationCheck the status of a pending domain verification. Triggers a DNS/HTTP check and returns the updated status. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this too
  • delete_domain_verificationDelete a domain verification attempt that is not verified (pending, verifying or failed) — nothing is revoked. A verified domain, or one that needs re-verification, is refused with domain_verified: removing it revokes it
  • wait_for_verification read-onlyPoll a verification until it reaches a terminal state (verified, failed, expired, revoked, or cancelled). Uses exponential backoff (2s initial, 1.5x, 30s max) with jitter. A multi-channel verification that lost the race
  • create_multi_channel_verificationCreate a multi-channel phone verification: one phone number challenged over several channels at once (OR / first-wins). The first channel the user completes wins, yields a single proof token, and cancels the losing sibli
  • get_multi_channel_verification_status read-onlyGet the status of a multi-channel verification group by its group_id. Returns the aggregate status (pending/verified/expired), the winning_channel once one completes, per-channel statuses, and the proof token (with expir
  • create_verification_requestCreate a multi-asset verification request. Allows verifying multiple assets (phone, email, domain, social, wallet, account, telegram_bot) in a single flow. Give the recipient the returned verification_url; wait_for_reque
  • get_verification_request read-onlyGet a verification request by ID. Returns the request with all its asset verification statuses. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. star
  • get_request_proofs read-onlyGet proof tokens for verified assets in a verification request. Returns proof tokens that can be used for offline verification. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate),
  • list_verification_requests read-onlyList verification requests with optional filters. Returns paginated results. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT op
  • get_request_by_reference read-onlyGet a verification request by its reference ID (your unique identifier). ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open t
  • cancel_verification_requestCancel a pending verification request. Only pending requests can be cancelled. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT
  • wait_for_request read-onlyPoll a verification request until it reaches a terminal state (completed, expired, or cancelled). Uses exponential backoff (2s initial, 1.5x, 30s max) with jitter. ACCESS: needs a Proof account. Authenticate this client
  • validate_proof read-onlyValidate a proof token online. Checks the token signature, expiry, and revocation status against the server, and optionally that the proof is about the identifier you expect. Public endpoint — no API key required.
  • get_proof_status read-onlyGet the status of a proof by its public handle (ph_ctl_* / ph_dlg_*) or a verification ID. Returns whether the proof is active, suspended, expired, or revoked — a live proof reads "active". ACCESS: needs a Proof account
  • revoke_proofRevoke a proof by its public handle (ph_ctl_* / ph_dlg_*) or a verification ID — the same addresses get_proof_status takes. The proof token will no longer validate anywhere: the status endpoint, the public validator, the
  • pause_proofPause a proof by its public handle (ph_ctl_* / ph_dlg_*) or a verification ID — a reversible stop, undone with resume_proof. While paused the proof is invalid: the status endpoint, the public validator and the Token Stat
  • resume_proofResume a proof paused with pause_proof, by the same handle (ph_ctl_* / ph_dlg_*) or verification ID: it validates again everywhere, and a resumed delegation is honoured again by gated publishers on their next status chec
  • list_revoked_proofs read-onlyGet the revocation list for offline proof validation. Returns a signed list of all revoked proof IDs. Reuse a fetched list for up to 5 minutes (its cache lifetime), then fetch it again to see new revocations; if you cann
  • get_proof_token read-onlyGet the current token of a proof you own, by its public ph_ctl_* handle. After a signing-key rotation this is the re-signed token, which replaces any older copy you hold. Each read is audited. A revoked or expired proof
  • list_reissued_proofs read-onlyList your proofs whose token was re-signed at or after an instant, oldest first — what to re-fetch after a signing-key rotation, for example when a webhook was missed. Items are references {proof_id, reissued_at, token_u
  • get_delegation_token read-onlyGet the current token of an active delegation by its public ph_dlg_* handle — after a signing-key rotation, the re-signed token to publish in place of the old one. Public endpoint — no API key required, since the token i
  • create_sessionCreate a new phone verification session. Returns deep_link, qr_code (base64 PNG), and qr_text (UTF-8 text QR for terminal display). Sessions provide a hosted verification flow with callbacks. Agent usage: After creating
  • get_session read-onlyGet a session by ID. Returns the session status, verification details, and proof token if verified. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again.
  • wait_for_session read-onlyPoll a session until it reaches a terminal state (verified, failed, or expired). Uses exponential backoff (2s initial, 1.5x, 30s max) with jitter. Before calling this for a challenge you created, make sure your reply te
  • list_my_proofs read-onlyList all verified assets for the authenticated user. Assets are verified identities (phones, emails, domains). ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this t
  • list_assets read-onlyDeprecated: use list_my_proofs
  • get_my_proof read-onlyGet a single verified asset by ID. Returns details including type, value, status, and verification timestamps. ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this t
  • get_asset read-onlyDeprecated: use get_my_proof
  • revoke_my_proofRevoke EVERY proof of one of your assets (a phone, email or domain), by its asset id from list_my_proofs — the asset stays on the account. A ph_ctl_* / ph_dlg_* handle is one proof, not an asset: revoke that with revoke_
  • revoke_assetDeprecated: use revoke_my_proof

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http proof-holdings https://api.proof.holdings/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.proof.holdings/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "proof-holdings": {
      "url": "https://api.proof.holdings/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "proof-holdings": {
      "type": "http",
      "url": "https://api.proof.holdings/mcp"
    }
  }
}

Questions

What does Proof Holdings do?

One API, all things verified — control, delegation, human approval, anti-impersonation. It exposes 80 tools to AI assistants.

What tools does Proof Holdings provide?

80 tools, including create_verification, get_verification, list_verifications, trigger_verification, submit_verification_code, resend_verification, test_verify, list_verified_users, get_verified_user, start_domain_verification, check_domain_verification, delete_domain_verification….

How do I connect Proof Holdings to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.proof.holdings/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Proof Holdings require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Proof Holdings online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Proof Holdings?

proof.holdings. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Automation & Integrations