Integration

Mailboxlayer integration

Mailboxlayer, by APILayer, checks email addresses in real time: syntax and typo check with a did-you-mean suggestion, MX record lookup, SMTP check that the mailbox exists, optional catch-all detection, role address, free provider and disposable provider detection, and a quality score from 0 to 1. One tool checks a single address; a bulk tool checks several in one request on the Professional Plus and Enterprise Plus plans. Plans are request quotas (the Free plan allows 100 requests a month for non-commercial use, without catch-all detection). Errors such as an invalid key or an exhausted quota come back with HTTP 200 and success false. Authentication is the API access key from your Mailboxlayer dashboard, sent as the access_key query parameter.

Connect Mailboxlayer How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Mailboxlayer

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.

bulk_validate_emailsBulk validate emailsGETChecks several email addresses in one request (Professional Plus: up to 25, Enterprise Plus: up to 100; other plans get an error). Returns one result per address. Errors arrive with HTTP 200 and success false.
validate_emailValidate emailGETChecks one email address: syntax, typo suggestion, MX records, SMTP mailbox check, catch-all (if requested), role, free and disposable provider, score 0..1. Errors arrive with HTTP 200, success false and an error object.

Use Mailboxlayer from Claude Code, Cursor or Codex

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

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