Integration

NeverBounce integration

NeverBounce verifies whether an email address is deliverable. Verify one address in real time and get its result code (valid, invalid, disposable, catchall or unknown), flags such as role account, free email host or disposable email, and a suggested correction for common typos; optionally the parsed address parts and the remaining credits. Check the account's paid and free credit balances and its bulk job counts. Errors are answered with HTTP 200 and a status other than success, so read status. The vendor reserves single verification for one-off checks such as a form submission, not for cleaning an existing list one address at a time. The bulk list verification routes (job create, parse, start, status, results, download, delete and search) and the widget confirmation route are not exposed. Authentication is a V4 API key (secret_...) from a Custom Integration app in the NeverBounce dashboard, sent as the key query parameter.

Connect NeverBounce How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with NeverBounce

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.

Account, 1 operation

get_account_infoGet account infoGETReturns the account's paid and free credits used and remaining, and the number of bulk verification jobs completed, under review, queued and processing. An error still answers HTTP 200: check status.

Email, 1 operation

verify_emailVerify emailGETVerifies one email in real time: result code (valid, invalid, disposable, catchall, unknown), address and domain flags, typo suggestion. Errors also answer HTTP 200: check status. One-off checks only: verifying a list one by one may lock the account.

Use NeverBounce from Claude Code, Cursor or Codex

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

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