Skip to content
EmailListChecker logo

EmailListChecker MCP server

Which servers in the official MCP registry are EmailListChecker's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to EmailListChecker

Whose server it is
  • Registry nameio.emaillistchecker/email-verificationverified in the MCP registry

The registry name sits under emaillistchecker.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools9
  • Server calls itselfEmaillistchecker.io
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 210 ms.

Measured dailydaily checks: 2, the first on 2026-10-19
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer652 ms
  • Space in an agent's context≈ 864 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsB · 81 of 100
  • Parameters without a description: in 1 of 9
  • Not saying whether it only reads or can destroy: 9 of 9

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers9 tools · read 2026-10-19
  • get_api_key

    Get your own free API key for this server (no account needed; 25 email verifications per day). Optional: the verification tools already work without a key on a shared trial. Returns the key once — reconnect with 'Authorization: Bearer…

  • get_credit_balance

    Get the current credit balance and a short usage summary for the account.

  • list_lists

    List the user's bulk verification lists/jobs, most recent first.

  • get_list

    Get the details of a single bulk verification list by its id.

  • explain_result

    Explain what a verification status or reason means in plain English, with a send recommendation. Covers valid, invalid, catch-all/accept-all, unknown, greylisted, disposable, role, free, spam-trap, abuse, do-not-mail, no-mx, disabled, and…

  • verify_email

    Verify the deliverability of a single email address. Returns a verdict (valid, invalid, risky, unknown). Costs 1 credit.

  • verify_batch

    Verify a batch of email addresses (up to 25 per call with an agent key). Returns per-email verdicts and saves a list. Costs 1 credit per email.

  • estimate_cost

    Estimate the credit cost of a verification before running it, and whether the user can afford it. Provide either a count of emails, a list_id to re-verify, or an operation ('single'/'finder'). Always quote this before proposing anything…

  • get_batch_status

    Get the progress and status of a bulk verification list/job by id.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "email-verification": {
      "type": "http",
      "url": "https://platform.emaillistchecker.io/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.