Integration

Mailcheck integration

Mailcheck email validation: check one address synchronously or submit a batch that is processed in the background, and get back a trust rate together with the checks behind it, whether the domain publishes mail servers, whether the mailbox answers, whether the domain accepts everything, and whether it is a throwaway provider. Public profiles tied to the address are reported when they exist. The key travels as a bearer token.

Connect Mailcheck How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Mailcheck use cases

rejecting throwaway addresses at signup
cleaning an imported mailing list before a campaign
recovering the identifier of a batch submitted earlier
waiting for a list cleaning batch to finish before continuing a workflow
validating a whole segment on a schedule
reporting progress of a long validation run
showing which validation batches are still running
cleaning an address before adding it to a mailing list

What you can do with Mailcheck

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 check, 3 operations

check_emails_batchCheck emails batchPOSTSubmits a batch of addresses for background validation.
get_batch_checkGet batch checkGETReads how far a batch check has got and where its results are.
list_batch_checksList batch checksGETReads the batch checks the account has submitted.

Email, 1 operation

check_emailCheck emailPOSTValidates a single email address and returns the verdict inline.

Use Mailcheck from Claude Code, Cursor or Codex

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

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

Mailcheck integration FAQ

What can you do with the Mailcheck integration?

LiveContext exposes 4 operations on Mailcheck, covering batch check and email. Common uses include rejecting throwaway addresses at signup, cleaning an imported mailing list before a campaign and recovering the identifier of a batch submitted earlier.