Integration

ValidatedMails integration

ValidatedMails verifies email addresses in real time. Check one address or a batch of up to 100 and get a four-state verdict (valid, risky, invalid, unknown) with a 0-100 score and syntax, MX, SMTP, catch-all, disposable, role and free-provider signals, or extract the email addresses, phone numbers and social links published on a public web page. Validation spends one prepaid credit per valid, risky or invalid result (unknown is free); discovery normally spends 2 credits when it finds a contact. Bulk CSV jobs, credit history, API key management and the console's sign-in, billing and admin routes are not exposed. Authentication is an API key created in the ValidatedMails console (API keys page), sent as a Bearer token in the Authorization header.

Connect ValidatedMails How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with ValidatedMails

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.

Email, 2 operations

validate_emailValidate emailPOSTVerifies one email address and returns its verdict in status (valid, risky, invalid or unknown; is_valid is true only for valid) with a 0-100 score and signals. Spends one credit unless the result is unknown.
validate_emails_batchValidate emails batchPOSTVerifies 1 to 100 email addresses in one call; results come back in input order, each with its own status or error. Spends one credit per valid, risky or invalid result; unknown ones are free.

Api key, 1 operation

check_api_keyCheck api keyGETChecks that the connected API key is accepted, without spending credits: answers ok true. Use it as a free connection test before any paid validation.

Contact, 1 operation

discover_contactsDiscover contactsPOSTFetches a public web page (static HTML, no JavaScript) and extracts its email addresses, phone numbers and social links; status says ok, unknown, blocked, timeout or invalid_url. Spends 2 credits only when status is ok.

Use ValidatedMails from Claude Code, Cursor or Codex

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

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