Skip to main content
Glama
BounceLens Email Check

BounceLens Email Check

Official
by bouncelens

BounceLens Email Check – MCP server

Lets Claude, Cursor and other MCP clients check email addresses before you send to them or save them. It finds:

  • Typos in the domain: jane@gmial.com → did you mean jane@gmail.com?

  • Disposable / throwaway domains (mailinator.com, 10minutemail and ~9,000 more)

  • Dead domains: the domain doesn't exist, has no mail server, or says it accepts no email (null MX)

  • Bad syntax, role addresses (info@, sales@), free providers, and duplicates (Gmail dot and +tag variants count as the same inbox)

  • The mail provider behind the domain (Google, Microsoft, Proofpoint, …)

Runs on your machine. No API key, no account, no sign-up. The only network calls are DNS lookups over HTTPS (Cloudflare 1.1.1.1). It uses the same checks as the free checker at bouncelens.com.

It never connects to the recipient's mail server, so it can't confirm that a mailbox exists. The best result is unconfirmed (format and domain OK). To check a whole CSV in your browser, use bouncelens.com.

Install

Requires Node.js 18 or newer. Setup guide for every client: bouncelens.com/mcp. Also listed on Smithery.

Claude Code

claude mcp add bouncelens -- npx -y github:bouncelens/mcp-email-check

Claude Desktop, Cursor, Windsurf and other clients. Add this to the client's MCP config (claude_desktop_config.json, .cursor/mcp.json, …):

{
  "mcpServers": {
    "bouncelens": {
      "command": "npx",
      "args": ["-y", "github:bouncelens/mcp-email-check"]
    }
  }
}

Grok Build

This repo is also a Grok Build plugin (.grok-plugin/plugin.json, .mcp.json and a skill in skills/). Install it from the plugin marketplace, or add the MCP server by hand with the same npx command as above.

From a clone

git clone https://github.com/bouncelens/mcp-email-check.git
cd mcp-email-check && npm install
# then use: "command": "node", "args": ["/path/to/mcp-email-check/index.js"]

Related MCP server: email-verify

Tools

Tool

Input

Returns

check_email

email (string)

One result

check_emails

emails (array, max 500)

summary with counts + one result per address, in input order

Each result (real output for a mistyped Outlook address):

{
  "input": "jane@outlok.com",
  "email": "jane@outlok.com",
  "status": "risky",
  "reasons": ["No MX record; mail would go to the website server", "Looks like a typo of outlook.com"],
  "flags": { "disposable": false, "role": false, "free": false, "duplicate": false, "gateway": false },
  "did_you_mean": "jane@outlook.com",
  "provider": null,
  "mx": null
}

status

Meaning

invalid

Will bounce: bad syntax, domain doesn't exist, no mail server, or null MX

risky

Disposable domain, likely typo, no MX record (mail would go to the web server), or the DNS lookup failed

unconfirmed

Format and domain OK. The mailbox itself isn't checked

Example prompts

  • "Check these sign-ups for fake or mistyped emails: …"

  • "Is jane@outlok.com a real address?"

  • "Clean this list: drop invalid and disposable addresses, fix the typos, remove duplicates."

Privacy

Addresses never leave your machine. Only the domain part is sent to Cloudflare's DNS-over-HTTPS resolver (1.1.1.1) to look up its MX/A records.

Development

npm install
npm test          # offline: DNS answers are faked

lib/engine.js and data/disposable.json are generated from the BounceLens main codebase, so change them there.

More from BounceLens

License

MIT. Disposable-domain list: disposable-email-domains (CC0).

Available Tools

2 tools
check_emailCheck one email addressA
Read-only

Check one email address for bad syntax, typos in the domain (gmial.com → gmail.com), disposable/throwaway domains, role addresses (info@, sales@) and domains that do not exist or have no mail server. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos.

Inputs: email (required).

check_emailsCheck a list of email addressesA
Read-only

Check up to 500 email addresses at once (same checks as check_email, plus duplicates, counting Gmail dot and +tag variants as the same inbox). Returns a summary with counts and one result per address, in input order. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos.

Inputs: emails (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    check_email and check_emails have clearly distinct purposes: one validates a single address, the other validates up to 500 in a batch. The descriptions explicitly differentiate them, and there is no functional overlap that would cause misselection.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (check_email, check_emails), with the plural form clearly indicating the batch operation. The naming is predictable and easy to infer.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but the server's narrow purpose (email validation) is well-covered by a single and a bulk tool. Each tool earns its place, and adding more would likely be redundant.

    Completeness5/5

    The surface fully covers the stated domain: single and bulk email validation with detailed statuses, typo suggestions, and duplicate handling. There are no obvious missing operations for the core task, and the limitation on mailbox checking is clearly disclosed.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables real-time email verification via MCP tools, checking syntax, MX, disposable domains, and optional SMTP probe to determine deliverability with a VALID/RISKY/INVALID verdict.
      2
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides email verification as an MCP tool, checking format, disposable domains, and mail server availability with structured results.
      ISC