Integration

Reoon Email Verifier integration

Reoon Email Verifier checks whether an email address is safe to send to: syntax, disposable or temporary domains, role accounts, spam traps, MX records and, in power mode, whether the inbox exists, is full or disabled and whether the domain is catch-all. Verify one address at a time, read the results of a bulk verification task by its id, and check the remaining daily and instant credits. Each verification result costs one Reoon credit (unknown results are refunded). Creating a bulk task is not exposed, because Reoon takes the API key inside that request's body. Authentication is an API key from the Reoon Email Verifier dashboard (API settings), sent as the key query parameter.

Connect Reoon Email Verifier How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Reoon Email Verifier

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 balance, 1 operation

check_account_balanceCheck account balanceGETReturns the remaining daily and instant verification credits of the account and whether the API key is active.

Bulk verification task, 1 operation

get_bulk_verification_task_resultGet bulk verification task resultGETReturns a bulk verification task's status (waiting, running, completed, file_not_found, file_loading_error) and progress; once completed, results holds every address's verification, keyed by address. Call again while waiting or running.

Email, 1 operation

verify_emailVerify emailGETVerifies one email address and returns its status and checks. mode=quick (default) is fast but skips the inbox check; mode=power checks the inbox and can take over a minute. Each result costs one Reoon credit; unknown results are refunded.

Use Reoon Email Verifier from Claude Code, Cursor or Codex

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

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