Integration

QuickEmailVerification integration

QuickEmailVerification checks whether an email address can receive mail before you send to it. Verify one address in real time and get its result (valid, invalid or unknown), the reason, disposable, role, free-provider and accept-all flags, a safe_to_send verdict, the MX record and a typo suggestion; a free sandbox endpoint returns predefined mock results for testing a workflow without spending credits. The bulk list verification routes (CSV file upload, job status, report download and job deletion) are not exposed. Authentication is an API key created under API Settings in the QuickEmailVerification account, sent as the apikey query parameter.

Connect QuickEmailVerification How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in QuickEmailVerification.Built from the 2 QuickEmailVerification tools below, on the connection you add once.

What you can do with QuickEmailVerification

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.

verify_emailVerify emailGETVerifies one email: valid, invalid or unknown with the reason (bad syntax, no domain or MX record, SMTP rejection...), disposable, role, free-provider, accept-all flags, safe_to_send, typo suggestion. Uses credits, unlike verify_email_sandbox.
verify_email_sandboxVerify email sandboxGETTest variant of verify_email: free, uses no credits, and returns a mock result chosen by the address's local part (valid@, disposable@, timeout@ and more: see the email parameter); any other address returns valid. For tests, never a real address.

Use QuickEmailVerification from Claude Code, Cursor or Codex

Connect QuickEmailVerification in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its QuickEmailVerification 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 QuickEmailVerification

Create your workspace
Sign up free. Nothing to install.
Connect QuickEmailVerification once
Add your QuickEmailVerification 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.