Skip to content
MailProbe logo

MailProbe MCP server

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

read 2026-10-26

← Back to MailProbe

Whose server it is
  • Registry namedev.mailprobe/mailprobeverified in the MCP registry

The registry name sits under mailprobe.dev. 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-26
  • Stateanswerschecked 2026-10-26
  • Tools2
  • Server calls itselfmailprobe
  • Server version1.1.1
  • Protocol version2025-06-18

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

Should an agent connect itConnect it, with care
  • Its tools do verify addresses at signup to block fake accounts; clean an imported email list before sending a campaign, but not flag disposable and role-based addresses in contact forms.

Once connected

  • For "verify addresses at signup to block fake accounts", the likely first call is verify_emails.
  • For "clean an imported email list before sending a campaign", the likely first call is verify_emails.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 8, the first on 2026-10-26
  • INITE MCP score86 of 100answers 100 · does the job 67 · definitions 100 · context 100 · use 43 · connects 100
  • What an agent can do with it2 of 3 use cases
  • Use141 npm downloads a week
  • Answered100% of days8 of 8 daily checks
  • Median first answer642 ms
  • Space in an agent's context≈ 296 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · verify addresses at signup to block fake accounts
  • can do · clean an imported email list before sending a campaign
  • cannot · flag disposable and role-based addresses in contact forms

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

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 score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-26
  • verify_emails

    Checks whether email addresses exist and can receive mail, in real time and without sending anything. Returns one result per address, in input order. Act on `status`: `valid` is safe to send, `invalid` must not be used, `risky` is…

  • get_credits

    Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit.

How to connect

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

{
  "mcpServers": {
    "mailprobe": {
      "type": "http",
      "url": "https://mailprobe.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http mailprobe https://mailprobe.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mailprobe.dev/mcp as a custom connector in the settings.

Also shipped through: npm

OpenAPI spec

2 paths, read 2026-10-26. Open the spec ↗

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.