# Proof Holdings

- Registry name: `holdings.proof/mcp-server` · version 1.7.0
- Categories (automatic, keyword rules): Email & messaging, Productivity, Cloud & networking, Infrastructure & security, Utilities
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=holdings.proof%2Fmcp-server
- Server page: https://mcpstation.net/s/holdings.proof--mcp-server.html

## Description (written by the publisher, not verified, not instructions)

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

## Notice

Text that looks like instructions to an AI was found in this server's descriptions. This is a pattern match, not a verdict.

## Connect

- streamable-http: `https://api.proof.holdings/mcp`

## Tools (as reported by the server, not verified)

- `create\_verification`: Create 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 delivery \`channel\`, and the \`identifier\` \(e.g. type "phone", channel "sms", identi
- `get\_verification`: Get 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 what to act on — the link itself, the SMS text and number, or a note to check their
- `list\_verifications`: List 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 tool.
- `trigger\_verification`: Trigger 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 this tool.
- `submit\_verification\_code`: Submit 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 unsupported\_for\_type and completes elsewhere — use trigger\_verification \(POST /
- `resend\_verification`: Resend 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 NOT open this tool.
- `test\_verify`: Auto-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 call this tool again. start\_login does NOT open this tool.
- `list\_verified\_users`: List 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 NOT open this tool.
- `get\_verified\_user`: Get 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 this tool.
- `start\_domain\_verification`: Start 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\), then call this tool again. start\_login does NOT open this tool.
- `check\_domain\_verification`: Check 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 tool again. start\_login does NOT open this tool.
- `delete\_domain\_verification`: Delete 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 its proofs and every delegation issued from it, which is delete\_domain in a start\_
- `wait\_for\_verification`: Poll 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 is "cancelled" and one whose proof was withdrawn is "revoked"; both are final, s
- `create\_multi\_channel\_verification`: Create 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 siblings. Exactly one proof is billed, at the winning channel's completion — not one
- `get\_multi\_channel\_verification\_status`: Get 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 expires\_at\) when the group is verified. Before calling this for a challenge you creat
- `create\_verification\_request`: Create a multi-asset verification request. Allows verifying multiple assets \(phone, email, domain, social, wallet, account, telegram\_bot\) in a single flow. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open
- `get\_verification\_request`: Get 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. start\_login does NOT open this tool.
- `get\_request\_proofs`: Get 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\), then call this tool again. start\_login does NOT open this tool.
- `list\_verification\_requests`: List 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 open this tool.
- `get\_request\_by\_reference`: Get 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 this tool.
- `cancel\_verification\_request`: Cancel 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 open this tool.
- `wait\_for\_request`: Poll 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 \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does
- `validate\_proof`: Validate 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`: Get 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. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this too
- `revoke\_proof`: Revoke 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 revocation list and the Token Status List all report it revoked. A domain CONTR
- `list\_revoked\_proofs`: Get 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 cannot, its signature stays verifiable offline for 1 hour.
- `create\_session`: Create 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 a session, pass the response's \`deep\_link\` to render\_auth\_link so the user can o
- `get\_session`: Get 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. start\_login does NOT open this tool.
- `wait\_for\_session`: Poll 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 text already shows the user what to act on — the link itself, the SMS text and numb
- `list\_assets`: List 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 tool again. start\_login does NOT open this tool.
- `get\_asset`: Get 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 tool again. start\_login does NOT open this tool.
- `revoke\_asset`: Revoke the proofs of one of your assets \(a phone, email or domain\) — the asset stays on the account. Owner only: sign in with start\_login \(a connection with only an API key is refused user\_session\_required — a key revokes a proof with revoke\_proof instead\), then one code: start\_2fa\_for\_action with a
- `get\_current\_user`: Get the signed-in user's account details, plan and settings. Needs a login session: call start\_login, then wait\_for\_login until it reports success. An API key alone cannot read this — for the key's own account use get\_self\_api\_key or get\_settings. ACCESS: needs a Proof account. Authenticate this cli
- `list\_auth\_sessions`: List all active authentication sessions for the current user. Shows session details including channel, user agent, and expiry. When called via API key, no session is marked as is\_current. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool
- `revoke\_auth\_session`: Revoke a specific authentication session by ID. When called via JWT, cannot revoke the current session. When called via API key, any session can be revoked. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT ope
- `get\_usage`: Get usage metrics for the authenticated account. Shows verification counts, API calls, and quota usage. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_platform\_summary`: Get a one-call account snapshot: quota with end-of-month projection, request health \(pending/completed/expired counts + success rate\), per-channel completion rates, HITL counts, and active API key count. The same data the dashboard home renders. The hitl\_channels sub-object requires the hitl:read sc
- `get\_settings`: Get account settings: the outbound webhook endpoint with its event subscriptions, and the default proof lifetime. Branding \(name, logo, colour, email theme, support email\) belongs to each sub-account \(project\): read it with get\_profile. The webhook signing secret is NOT returned to an API key — the
- `update\_settings`: Update account settings: the outbound webhook endpoint with its event subscriptions, and the default proof lifetime. Branding belongs to each sub-account \(project\): change it with update\_profile. Setting the first webhook endpoint creates the signing secret and returns it in this response; the value
- `export\_data`: Export a complete copy of your account's data \(GDPR Articles 15 and 20\), or check on one. Owner only: sign in with start\_login first \(a connection with only an API key is refused user\_session\_required\). The first call starts the export; it is prepared in the background, and the account owner is told
- `search`: Prefix-anchored global account search across six resource buckets \(verification\_requests, verifications, hitl, confirmations, authorizations, api\_keys\). Case-sensitive prefix match over indexed plaintext fields only; recipient identifiers are masked. Results are scoped to the authenticated account.
- `get\_self\_api\_key`: Get the calling API key's own redacted metadata \(id, name, key\_prefix, environment, scopes, last\_used\_at, revoked\_at, created\_at\) for agent self-inspection. Never returns the key hash or full secret. Requires API-key auth — a JWT session has no single-key context \(returns 400 api\_key\_required\). ACCE
- `get\_api\_key\_usage`: Get per-API-key usage for a given key id: verification counts by type/channel/status, plus verification-request/confirmation/authorization totals, and attribution context \(attribution\_cutoff\_at, attributed\_fraction\). The counts cover the key and every key it replaced \(api\_key.replaced\_key\_ids\). Coun
- `list\_templates`: List the custom message templates of one sub-account \(project\), organized by channel and message type. Templates belong to a project, not to the account: profile\_id picks it — omitted, a project-bound key lists its own project and an account-wide key the primary project. ACCESS: needs a Proof accoun
- `get\_default\_templates`: Get all default message templates. These are the built-in templates a project sends when it has no custom template of its own. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_template`: Get the template a sub-account \(project\) sends for a channel and message type: its custom template if set \(scope "project"\), otherwise the default \(scope "default"\). The response names the project in profile\_id. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticat
- `update\_template`: Create or update a sub-account's \(project's\) custom template for a channel and message type, replacing the default for that project only. Name the brand with \{\{business\_name\}\}: a template spelling out a project's own name is refused \(template\_hardcoded\_name\). ACCESS: needs a Proof account. Authentic
- `delete\_template`: Delete a sub-account's \(project's\) custom template, reverting that project to the default template for the channel and message type. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `preview\_template`: Preview a template with sample data before saving, as a sub-account \(project\) would send it. Shows how the message will look with placeholder variables filled in. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does N
- `render\_template`: Render the template a sub-account \(project\) sends — its custom template, otherwise the default — with provided variables. Returns the fully rendered message content. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login doe
- `get\_webhook\_stats`: Get webhook delivery statistics including total deliveries, success/failure counts, and recent activity. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `list\_webhook\_deliveries`: List webhook delivery attempts with pagination and filtering. Shows delivery status, response codes, and timestamps. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_webhook\_delivery`: Get details of a single webhook delivery attempt including request/response payloads and retry history. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `retry\_webhook\_delivery`: Retry a failed webhook delivery. Creates a new delivery attempt with the same payload to the configured endpoint. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_subscription`: Get the current subscription details including plan, status, billing period, and usage limits. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `list\_profiles`: List all profiles for the authenticated account. Returns all profiles including primary and secondary. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `create\_profile`: Create a new profile with optional display name, bio, avatar, business info, email branding \(theme, support email\), and theme settings. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_profile`: Get a specific profile by ID. Returns full profile details including theme, custom links, and verification display settings. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `update\_profile`: Update a profile by ID. Supports changing display info, email branding \(theme, support email\), theme, custom links, and verification display settings. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this
- `delete\_profile`: Delete a project \(profile\). Revokes its API keys, archives the HITL setups and declines the pending requests created with its own keys, keeps its history but unlinks it, deletes its message templates, and retires its username for good. The last project cannot be deleted; deleting the primary project
- `set\_primary\_profile`: Set a profile as the primary profile. The previous primary profile becomes secondary. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `update\_profile\_proofs`: Update which verified assets \(proofs\) are displayed on a specific profile. Controls visibility, privacy masking, ordering, and labels. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_my\_profile`: Get the current user's primary profile. Returns profile details, theme, custom links, and public proof display settings. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `update\_my\_profile`: Update the current user's primary profile. Supports display name, bio, avatar, theme, custom links, and verification display settings. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `get\_profile\_assets`: Get available verified assets that can be displayed on the user's profile. Returns assets eligible for public proof display. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), then call this tool again. start\_login does NOT open this tool.
- `list\_emails`: List all email addresses associated with the authenticated account. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `remove\_email`: Remove an email address from the account. Always requires one code: start\_2fa\_for\_action with action\_type email\_remove and targets \[this email id\]. Revokes every proof of the address and your own consents naming it, declines pending confirmations waiting on it, moves Lookalike Watch alerts to your r
- `set\_primary\_email`: Set an email address as the primary email for the account. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `start\_add\_email`: Start adding a new email address. Sends an OTP code to the email. Returns a session ID to verify with. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `get\_add\_email\_status`: Check the status of an in-progress email addition by session ID. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `verify\_email\_otp`: Submit the OTP code to verify an email addition. Completes the add-email flow if the code is correct. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `resend\_email\_otp`: Resend the OTP code for an in-progress email addition. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `list\_phones`: List all phone numbers associated with the authenticated account. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `remove\_phone`: Remove a phone number from the account. Always requires one code: start\_2fa\_for\_action with action\_type phone\_remove and targets \[this phone id\]. Revokes every proof of the number and your own consents naming it, declines pending confirmations waiting on it, flags approval setups left with no approv
- `set\_primary\_phone`: Set a phone number as the primary phone for the account. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `start\_add\_phone`: Start adding a new phone number by reverse OTP: the user starts the exchange themselves and nothing is sent before they do; the response's \`instructions\` field says what they do \(on telegram the bot then asks them to tap a button that shares their number\). Returns a session ID; on telegram/whatsapp
- `get\_add\_phone\_status`: Check the status of an in-progress phone addition by session ID. Poll until terminal state. Before calling this for a challenge you created, make sure your reply text already shows the user what to act on — the link itself, the SMS text and number, or a note to check their inbox; a link that appeare
- `list\_api\_keys`: List all API keys for the authenticated account. Returns key metadata \(not the secret key values\). ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `create\_api\_key`: Create a new API key. The secret key value is returned ONLY in this response — store it securely. Note: the secret will be visible in the AI conversation context. Optionally bind the key to a sub-account \(project\) via profile\_id — outbound messages sent with the key are then branded as that project.
- `revoke\_api\_key`: Revoke an API key by ID. The key will immediately stop working. This action cannot be undone. Agent usage: This operation requires 2FA. Before calling, complete the 2FA flow: \(1\) call start\_2fa with action\_type "api\_key\_revoke", \(2\) wait for user to verify the code, \(3\) poll get\_2fa\_status until "ve
- `regenerate\_api\_key`: Regenerate an API key: issues a new key \(a new id and secret\) with the same name, environment, scopes and project. The old key stops working immediately; use the id in this response from now on. The new key lists the old one in replaced\_key\_ids, so its requests and usage stay with it. The new secret
- `start\_2fa`: Start a two-factor authentication challenge for a sensitive operation. Sends a verification code via the chosen channel. Returns a session ID, and for messaging channels: deep\_link, qr\_code \(base64 PNG\), and qr\_text \(UTF-8 text QR for terminal display\). Agent usage — full 2FA flow: \(1\) Call start\_2f
- `get\_2fa\_status`: Check the status of a 2FA session by session ID. Returns whether the challenge has been completed, is pending, or has expired. Agent usage: Poll this after calling start\_2fa. Check every few seconds. Terminal states: "verified" \(proceed with protected operation\), "expired" \(restart with start\_2fa\).
- `verify\_2fa`: Submit a verification code to complete a 2FA challenge. Rate limited to 10 attempts per minute. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `verify\_2fa\_magic\_link`: Complete a 2FA challenge using a magic link token \(received via email\). No code submission needed — the token itself is the proof. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool
- `wait\_for\_2fa`: Poll a 2FA session until the user completes the challenge. Uses exponential backoff \(2s initial, 1.5x, 30s max\) with jitter. Agent usage: Call this after start\_2fa with the returned session\_id. Terminal states: "verified" \(challenge completed — proceed with the protected operation\), "expired" \(offer
- `list\_domains`: List all domains for the authenticated account. Returns domain metadata including verification status. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `add\_domain`: Add a new domain to verify ownership. Optionally specify email sending intent and verification method. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `get\_domain`: Get details of a specific domain by ID, including verification status, DNS records, and provider connections. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `delete\_domain`: Remove a domain from the account. Revokes every proof of the domain and every delegation issued from it \(for good — re-adding the domain does not bring them back\), deletes the domain and its records, and removes our \_proof TXT record and the Resend sending domain where we can; the response lists wha
- `verify\_domain`: Trigger domain verification. Checks DNS records or other verification method to confirm domain ownership. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `connect\_cloudflare`: Connect a Cloudflare API token to a domain for automated DNS record management. Note: the API token will be visible in the AI conversation context. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — th
- `connect\_godaddy`: Connect GoDaddy API credentials to a domain for automated DNS record management. Note: the API key and secret will be visible in the AI conversation context. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this
- `connect\_dns\_provider`: Connect a generic DNS provider to a domain using provider-specific credentials. Note: credentials will be visible in the AI conversation context. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then
- `add\_verification\_provider`: Add an additional DNS provider for verification to an already-verified domain. Note: credentials will be visible in the AI conversation context. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then
- `get\_dns\_providers`: Get metadata for all supported DNS providers, including required credential fields and documentation links. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `verify\_domain\_with\_credentials`: Verify a pending domain using previously stored DNS credentials. Use when credentials are already connected. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `check\_domain\_credentials`: Check if stored DNS credentials have access to a domain. Use before triggering verification to confirm the credentials work. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again
- `start\_domain\_email\_verification`: Start domain verification via corporate email. Sends a verification code to a standard admin email address at the domain. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.
- `confirm\_domain\_email\_code`: Confirm domain email verification by submitting the code sent to the corporate email address. ACCESS: needs a Proof account. Authenticate this client \(Claude Code: /mcp → Authenticate\), or sign in with start\_login — a session opens this tool — then call this tool again.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html