Integration

BounceLens integration

BounceLens checks email addresses before you send to them or store them: bad format, a domain that does not exist or has no mail server (MX), likely typos with a suggested correction (gmial.com to gmail.com), disposable (throwaway) domains, role addresses (info@, sales@), free providers, security gateways and duplicates, plus the mail provider behind the domain. It never logs in to mail servers, so it cannot confirm that a mailbox exists: the best result is unconfirmed (format and domain OK). Check one address or up to 500 in one call (at most 20 different domains per call); the vendor allows 20 calls per 10 seconds per IP address and asks that you only check lists you have a lawful reason to hold. No authentication: the API is free, keyless and stores none of the addresses it receives.

Connect BounceLens How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with BounceLens

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

check_emailCheck emailGETAgents: ask firstChecks one email address (personal data, echoed back) for format, domain and MX, likely typos, disposable domain, role inbox, free provider and gateway. Status is invalid, risky or unconfirmed; a mailbox is never confirmed.
check_emailsCheck emailsPOSTAgents: ask firstChecks 1 to 500 email addresses (personal data, echoed back) in one call, at most 20 different domains: one result per address in the order sent, plus totals. Duplicates (Gmail dots and +tags ignored) are flagged.

Use BounceLens from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect BounceLens once
BounceLens needs no credential, so its tools work immediately.
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.