List your agent

Proof Holdings

MCP server● Hosted · onlineInstallablev1.13.0

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

Reviews

No review yet. Used Proof Holdings? Be the first to help others choose.

What it does

Proof Holdings is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version1.13.0
Packagesnpm
PriceNot in the registry
First seen26 Sept 2026
Last checked4h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

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

In Claude Code: claude mcp add --transport http proof-holdings https://api.proof.holdings/mcp

Install package

  • NPM @proof-holdings/mcp-server v1.13.0 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "proof-holdings": {
      "url": "https://api.proof.holdings/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Proof Holdings answered an MCP connection on 15 Nov 2026 and introduced itself as proof-holdings 1.11.0 (MCP protocol 2025-06-18).

217 tools offered to AI assistants

  • 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`, an
  • 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 li
  • 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_typ
  • 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.
  • 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 a
  • 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
  • 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 d
Show 88 more
  • 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 o
  • 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 pro
  • 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 grou
  • 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. Give the recipient the returned verification_url; wait_for_request or get_verificati
  • 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
  • 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
  • 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 →
  • 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 c
  • 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
  • pause_proof · Pause 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 Status List report it su
  • resume_proof · Resume 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 check. Only the paused r
  • 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 st
  • get_proof_token · Get 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 answers proof_not_li
  • list_reissued_proofs · List 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_url}, never tokens: p
  • get_delegation_token · Get 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 is already published
  • 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
  • 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
  • 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
  • list_my_proofs · 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_logi
  • list_assets · Deprecated: use list_my_proofs
  • get_my_proof · 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_logi
  • get_asset · Deprecated: use get_my_proof
  • revoke_my_proof · Revoke 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_proof. Owner only: s
  • revoke_asset · Deprecated: use revoke_my_proof
  • 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_se
  • list_auth_sessions · List the current user's signed-in devices: every session that can still renew, idle ones included. Each shows its channel, user agent and expires_at, which is when the session stops being able to renew (not when its current access token exp
  • revoke_auth_session · Sign out one device (session) by ID. Over a signed-in session it cannot end the current one (that is logout). Over an API key it can end any of the account's sessions. NOT AVAILABLE HERE: This tool is not available on the hosted Proof MCP s
  • 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
  • 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, approval channel counts, and active API key count. The same data the dashbo
  • 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: read it with get_sub_account. The webho
  • update_settings · Update account settings: the outbound webhook endpoint with its event subscriptions, and the default proof lifetime. Branding belongs to each sub-account: change it with update_sub_account. Setting the first webhook endpoint creates the sig
  • 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
  • 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 a
  • 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 ha
  • 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 ke
  • get_company · Get the account company profile: legal name, registration code, country, EU VAT number, billing address and billing email, with the state of the VAT number VIES check. company is null before one is saved. Needs settings:read on an account-w
  • list_templates · List the custom message templates of one sub-account, organized by channel and message type. Templates belong to a sub-account, not to the account: profile_id picks it — omitted, a sub-account key lists its own sub-account and an account-wi
  • get_default_templates · Get the default message templates — one for each channel and message type a message is actually sent for. These are the built-in templates a sub-account sends when it has no custom template of its own. ACCESS: needs a Proof account. Authent
  • get_template · Get the template a sub-account sends for a channel and message type: its custom template if set (scope "project"), otherwise the default (scope "default"). The response names the sub-account in profile_id. ACCESS: needs a Proof account. Aut
  • update_template · Create or update a sub-account's custom template for a channel and message type, replacing the default for that sub-account only. Name the brand with {{business_name}}: a template spelling out a sub-account's own name is refused (template_h
  • delete_template · Delete a sub-account's custom template, reverting that sub-account 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 aga
  • preview_template · Preview a template with sample data before saving, as a sub-account 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 → Authentica
  • render_template · Render the template a sub-account 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 → Authent
  • 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
  • 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. star
  • 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
  • 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_l
  • list_webhook_endpoints · List the account's webhook endpoints (URL, events, scope, sub-accounts, status). Secrets are never listed. A sub-account key sees only the endpoints scoped to exactly its own sub-account. ACCESS: needs a Proof account. Authenticate this cli
  • get_webhook_endpoint · Get one webhook endpoint by ID. The signing secret is not returned (only create_webhook_endpoint and rotate_webhook_endpoint_secret return it). ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then
  • create_webhook_endpoint · Add a webhook endpoint. An event reaches every active endpoint whose scope includes the event's sub-account and whose events match; an account-level event reaches "all"-scope endpoints only. An account still delivering to the single webhook
  • update_webhook_endpoint · Update a webhook endpoint: its URL, events, scope, sub-accounts, status or description. Every field is optional, but send at least one. Changing the scope to "selected" without profile_ids keeps the stored list. The signing secret is unchan
  • delete_webhook_endpoint · Delete a webhook endpoint. It receives no new events; deliveries already queued to it are still attempted, signed with the secret they were queued with. Cannot be undone. ACCESS: needs a Proof account. Authenticate this client (Claude Code:
  • rotate_webhook_endpoint_secret · Replace a webhook endpoint's signing secret and return the new one — this and create_webhook_endpoint are the only times a secret is returned, so store it now. New deliveries are signed with the new secret; deliveries already queued keep th
  • 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
  • get_balance · Get the prepaid balance (in euro cents and mills), the low-balance threshold, the top-up amounts on offer and the auto top-up setting. Proofs past the plan's included amount are drawn from this balance; once billing is live, an account whos
  • list_balance_ledger · List the prepaid balance history, newest first: every top-up, refund and adjustment, and one usage row per month for that month's deductions. Amounts are signed euro cents (credits positive). ACCESS: needs a Proof account. Authenticate this
  • list_sub_accounts · List every sub-account of the authenticated account, the primary one included. 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 · Deprecated: use list_sub_accounts
  • create_sub_account · Create a new sub-account 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 cal
  • create_profile · Deprecated: use create_sub_account
  • get_sub_account · Get one sub-account by ID, with its full 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_
  • get_profile · Deprecated: use get_sub_account
  • update_sub_account · Update a sub-account 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 → Authenti
  • update_profile · Deprecated: use update_sub_account
  • delete_sub_account · Delete a sub-account. Revokes its API keys, archives the approval channels 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
  • delete_profile · Deprecated: use delete_sub_account
  • set_primary_sub_account · Make a sub-account the primary one. The previous primary sub-account 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 to
  • set_primary_profile · Deprecated: use set_primary_sub_account
  • update_sub_account_page_proofs · Update which verified assets (proofs) are displayed on one named sub-account. Controls visibility, privacy masking, ordering, and labels. For the primary sub-account in a signed-in session, update_public_page_proofs does the same. ACCESS: n
  • update_profile_proofs · Deprecated: use update_sub_account_page_proofs
  • get_current_sub_account · Get the current sub-account record: with a sub-account key, that key's own sub-account; otherwise the account's primary sub-account. The first call creates a primary sub-account if the account has none (never for a sub-account key, which ge
  • get_my_profile · Deprecated: use get_current_sub_account
  • update_public_page · Update the record get_current_sub_account reads: a sub-account key's own sub-account, otherwise the primary sub-account (never creates one). Takes presentation fields only — display name, bio, avatar, theme, custom links, and verification d
  • update_my_profile · Deprecated: use update_public_page
  • list_public_page_proof_options · List the verified proofs that can be shown on the Public page (each one eligible to be listed with update_public_page_proofs). ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool a
  • get_profile_assets · Deprecated: use list_public_page_proof_options
  • rotate_callback_secret · Rotate a sub-account's callback signing secret — the secret that signs every callback_url delivery of its verification requests — and return the new one. This is the only time it is returned, so store it now. Callback deliveries already que
  • preview_sub_account_deletion · Preview what delete_sub_account would do to one sub-account, without changing anything: the counts the dashboard Delete sub-account dialog shows and the sub-account that would take its place, or why deletion is refused (allowed: false). Nee
  • preview_profile_deletion · Deprecated: use preview_sub_account_deletion
  • list_emails · List all email addresses associated with the authenticated account. ACCESS: needs a Proof account, signed in: call start_login, show the user its challenge, then wait_for_login, then call this tool again. Authenticating this client alone do
  • 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 confirm
  • set_primary_email · Set an email address as the primary email for the account. Always requires one code: start_2fa_for_action with action_type email_primary (no targets); without it the call answers 403 2fa_required. ACCESS: needs a Proof account, signed in: c
  • start_add_email · Start adding a new email address. Sends an OTP code to the email. Returns a session ID: when the user has the code, pass it with that session ID to verify_email_otp (resend_email_otp if it did not arrive; get_add_email_status reads the sess
  • get_add_email_status · Check the status of an in-progress email addition by session ID. ACCESS: needs a Proof account, signed in: call start_login, show the user its challenge, then wait_for_login, then call this tool again. Authenticating this client alone does

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install package@proof-holdings/mcp-serverDECLAREDSRC-001 Official MCP Registry4h ago
Version1.13.0DECLAREDSRC-001 Official MCP Registry4h ago
Hosted endpointhttps://api.proof.holdings/mcpDECLAREDSRC-001 Official MCP Registry4h ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry4h ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry4h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry4h ago
Websitehttps://proof.holdingsDECLAREDSRC-001 Official MCP Registry4h ago
Repositoryhttps://github.com/ProofHoldings/mcp-serverDECLAREDSRC-001 Official MCP Registry4h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry4h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry4h ago

Change history

  • VERSION16 Nov 2026
    1.12.0 → 1.13.0
  • VERSION16 Nov 2026
    1.11.0 → 1.12.0
  • VERSION15 Nov 2026
    1.10.0 → 1.11.0
  • VERSION12 Nov 2026
    1.9.0 → 1.10.0
  • VERSION12 Nov 2026
    1.8.4 → 1.9.0
  • VERSION11 Nov 2026
    1.8.3 → 1.8.4
  • VERSION10 Nov 2026
    1.8.2 → 1.8.3
  • VERSION10 Nov 2026
    1.8.1 → 1.8.2
  • VERSION09 Nov 2026
    1.8.0 → 1.8.1
  • VERSION05 Nov 2026
    1.7.2 → 1.8.0
  • VERSION03 Nov 2026
    1.7.1 → 1.7.2
  • VERSION26 Oct 2026
    1.7.0 → 1.7.1
  • VERSION16 Oct 2026
    1.6.0 → 1.7.0
  • VERSION14 Oct 2026
    1.5.0 → 1.6.0
  • VERSION13 Oct 2026
    1.4.0 → 1.5.0
  • VERSION09 Oct 2026
    1.3.0 → 1.4.0
  • VERSION08 Oct 2026
    1.1.0 → 1.3.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Proof Holdings? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Proof HoldingsLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Proof Holdings?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/proof-holdings?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/proof-holdings/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Proof Holdings

How do I connect Proof Holdings?

Use the hosted endpoint https://api.proof.holdings/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Proof Holdings offer?

When Electra Index connected on 15 Nov 2026, it listed 217 tools: create_verification, get_verification, list_verifications, trigger_verification, submit_verification_code, resend_verification, test_verify, list_verified_users and more. The full list is in "Live check" above.

Is Proof Holdings online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.