Integration

MailerCheck integration

MailerCheck verifies email addresses and cleans email lists. Check one address in real time or asynchronously (valid, catch_all, mailbox_full, role, unknown, syntax_error, typo, mailbox_not_found, disposable, blocked or error), create a list from emails or an uploaded CSV or TXT file, start its verification, read per-result statistics and each email's result, delete lists, and read the account, user and credit balance. Each verification spends 1 credit. Email Insights and Inbox Placement are not in the public API. Authentication: an API token (profile picture, API, Create token), sent as a Bearer token.

Connect MailerCheck How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with MailerCheck

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 list, 6 operations

create_listCreate listPOSTCreates an email list from a name and an array of email addresses. It is not verified yet: call verify_list with the returned id to start (that spends credits).
delete_listDelete listDELETEPermanently deletes the email list with the given id, with its results. Answers 204 with no content.
get_listGet listGETReturns one email list: name, source, email count, verification start and end times, status (not_started, processing, done) and how many of its emails got each result (valid, catch_all, typo...).
list_listsList listsGETLists the account's email lists, each with its status (not_started, processing, done), email count and per-result statistics. Page with page and limit; meta.last_page and links.next tell whether more pages exist.
upload_listUpload listPOSTCreates an email list from an uploaded CSV or TXT file of addresses. It is not verified yet: call verify_list with the returned id to start (that spends credits).
verify_listVerify listPUTStarts verifying a list, spending 1 credit per email. Returns the list with status processing; follow it with get_list. Refused with 402 when credits are short, 409 when verification already started.

Email verification, 3 operations

create_async_checkCreate async checkPOSTQueues a check of one email address and returns its id at once (state queued), to avoid delays and timeouts. Read the result with get_async_check. Spends 1 credit.
get_async_checkGet async checkGETReturns an asynchronous check's state (queued, then completed) and, once completed, its result (valid, catch_all, typo, mailbox_not_found and the other results). Pass the id from create_async_check.
verify_emailVerify emailPOSTVerifies one email address in real time and returns status: valid (safe to send), catch_all, mailbox_full, role, unknown (risky), syntax_error, typo, mailbox_not_found, disposable, blocked (do not send) or error. Spends 1 credit.

Account, 1 operation

get_accountGet accountGETReturns the MailerCheck account tied to the API token: name, credit balance, and the company and address details stored on it (may be null).

Credit balance, 1 operation

get_creditsGet creditsGETReturns the number of verification credits left on the account (total); 1 credit verifies 1 email.

Email list result, 1 operation

list_list_resultsList list resultsGETReturns a list's emails with their verification result (valid, catch_all, typo, mailbox_not_found...), page by page; result filters by one result type. The addresses are personal data.

User, 1 operation

get_userGet userGETReturns the MailerCheck user who created the API token: name, email, newsletter subscription, email verification and terms acceptance times. Personal data.

Use MailerCheck from Claude Code, Cursor or Codex

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

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