Integration

Catch-all Verifier integration

Catch-all Verifier checks whether email addresses, including those on catch-all (accept-all) domains that other verifiers report as risky or unknown, really accept mail, and answers valid or invalid for each one. Submit one address with verify_email or a list of up to 5,000 with verify_email_list, then read the outcome by the returned id with get_email_verification or get_email_list_verification, and check the remaining credit balance with get_credit_balance. Every verification is billed in prepaid credits, one credit per address (the pricing page sells packs from 2,500 credits for $25, about $0.01 per address, to 100,000 credits for $399, and credits never expire); a submission on an empty balance is refused with HTTP 403 Insufficient credits. The optional result webhook of the single verification is not exposed. Authentication is the API key shown on the API settings page of the Catch-all Verifier app, sent as is (no prefix) in the Authorization header.

Connect Catch-all Verifier How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Catch-all Verifier.Built from the 5 Catch-all Verifier tools below, on the connection you add once.

What you can do with Catch-all Verifier

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Email verification, 4 operations

get_email_list_verificationGet email list verificationGETReturns the results of a list verification started with verify_email_list: items with each email and its valid or invalid result when finished, or message and stats (requested, finished) while still running. Free read.
get_email_verificationGet email verificationGETReturns the result of one email verification started with verify_email: the email and its result, valid or invalid. Pass the id verify_email returned. Free read.
verify_emailVerify emailPOSTStarts a real, billed verification of one email address (1 credit, about $0.01) and returns the task id. Pass that id to get_email_verification for the result.
verify_email_listVerify email listPOSTStarts a real, billed verification of 1 to 5,000 email addresses (1 credit each, about $0.01) and returns the task id. Pass it to get_email_list_verification.

Credit balance, 1 operation

get_credit_balanceGet credit balanceGETReturns the remaining prepaid credit balance of the account. Free read; check it before a large verify_email_list.

Use Catch-all Verifier from Claude Code, Cursor or Codex

Connect Catch-all Verifier in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Catch-all Verifier operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Catch-all Verifier

Create your workspace
Sign up free. Nothing to install.
Connect Catch-all Verifier once
Add your Catch-all Verifier connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.