Integration

Kickbox integration

Kickbox verifies email addresses. Verify one address in real time and get its result (deliverable, undeliverable, risky or unknown), the reason, role, free, disposable and accept-all flags, a Sendex quality score and a typo suggestion; or upload a list of up to 1 million addresses as a batch job, then read its status, result stats and a download URL for the results file. Each verification consumes credits, except with a sandbox key (test_...), which answers mock results. The free disposable-domain check, served from a separate keyless host, is not exposed. Authentication is a Kickbox API key (live_... or test_...) sent as a Bearer token in the Authorization header. EU-only accounts use a different host and are not supported here.

Connect Kickbox How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Kickbox

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.

Batch verification, 2 operations

get_batch_verificationGet batch verificationGETReturns a batch job's status (starting, processing, completed, failed), progress counters, and once completed the result stats and a results download_url valid for one hour (call again for a fresh one).
start_batch_verificationStart batch verificationPUTStarts an async verification of a file of up to 1 million emails (one per line or CSV, under 250 MB); consumes credits. Returns id: poll get_batch_verification with it until status is completed.

Email, 1 operation

verify_emailVerify emailGETVerifies one email in real time: result (deliverable, undeliverable, risky, unknown), reason, role/free/disposable/accept_all flags, Sendex score, typo suggestion. Consumes one credit (a test_ sandbox key answers mock results).

Use Kickbox from Claude Code, Cursor or Codex

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

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