Email Validator

io.github.lazymac2xPublished by GitHub account lazymac2xv1.0.0Updated Oct 24, 2026

Cloudflare Workers MCP server: email-validator

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that validates email addresses: syntax, MX/SPF/DKIM, disposable and role detection, typo fixes and risk scores.

What you can do
  • Validate one address with syntax, MX, SPF/DKIM, disposable and role checks plus a 0-100 risk score
  • Validate up to 100 addresses in one batch and get per-address results with summary counts
  • Check a domain's reputation: MX, SPF, DKIM, A record, disposable status and overall score
  • Suggest corrections for common typos in popular mailbox domains such as Gmail, Outlook or iCloud
When to use it
Useful when an assistant has to screen signup or contact lists, clean a mailing list before sending, or flag risky, disposable or mistyped addresses before they reach a CRM or email tool.
Requirements
A remote MCP endpoint; no package, account, API key or header is declared. The server performs DNS and domain lookups on its side, so the assistant only needs network access to the endpoint.
Before you install
Email addresses submitted for validation are sent to a third-party hosted service, so avoid sending sensitive personal data. The README advertises paid Pro tiers and referral links; the free tier's call limits are not stated. Results are heuristic risk scores, not proof that a mailbox exists.

Installation

In SourceWeft

  1. Open Email Validator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lazymac2x%2Femail-validator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "email-validator": {
      "type": "http",
      "url": "https://api.lazy-mac.com/email-validator/mcp"
    }
  }
}

README

[logo]

[lazymac API Store] [Gumroad] [MCPize]

email-validator-api

⭐ Building in public from $0 MRR. Star if you want to follow the journey — lazymac-mcp (42 tools, one MCP install) · lazymac-k-mcp (Korean wedge) · lazymac-sdk (TS client) · api.lazy-mac.com · Pro $29/mo.

[npm] [Smithery] [lazymac Pro] [api.lazy-mac.com]

🚀 Want all 42 lazymac tools through ONE MCP install? npx -y @lazymac/mcp · Pro $29/mo for unlimited calls.

Comprehensive email validation API — syntax (RFC 5322), MX record lookup, disposable domain detection, role-based detection, SPF/DKIM checks, typo suggestions, and risk scoring (0-100). REST + MCP server.

Quick Start

bash
npm install && npm start  # http://localhost:3100

Endpoints

Validate Email

bash
curl -X POST http://localhost:3100/validate \  -H "Content-Type: application/json" \  -d '{"email": "[email protected]"}'# → {email, syntax, role, disposable, mx, domain, spf, dkim, typo, risk, deliverable}

Batch Validate (up to 100)

bash
curl -X POST http://localhost:3100/validate/batch \  -H "Content-Type: application/json" \  -d '{"emails": ["[email protected]", "[email protected]"]}'# → {total, valid, invalid, results}

Domain Check

bash
curl -X POST http://localhost:3100/domain \  -H "Content-Type: application/json" \  -d '{"domain": "gmail.com"}'# → {domain, exists, mx, spf, dkim, is_disposable, is_free_provider, reputation_score}

Typo Suggestion

bash
curl -X POST http://localhost:3100/suggest \  -H "Content-Type: application/json" \  -d '{"email": "[email protected]"}'# → {original, has_suggestion, suggested: "[email protected]", reason}

MCP (JSON-RPC 2.0)

bash
curl -X POST http://localhost:3100/mcp \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

MCP Tools: validate_email, validate_batch, check_domain, suggest_fix

License

MIT

Related projects

💡 Host your own stack? Get $200 DigitalOcean credit via lazymac referral link.

Source: README.md at commit 17cbc31

Tools

4

validate_email

Validate a single email address with comprehensive checks: syntax (RFC 5322), MX records, disposable domain detection, role-based detection, SPF/DKIM, typo suggestions, and risk scoring (0-100).

Parametersemailrequired

validate_batch

Batch validate up to 100 email addresses at once. Returns individual results plus summary stats.

Parametersemailsrequired

check_domain

Check domain reputation: MX records, SPF, DKIM, disposable detection, A record existence, and overall reputation score.

Parametersdomainrequired

suggest_fix

Detect common email typos and suggest corrections (e.g. [email protected] -> [email protected]). Covers Gmail, Yahoo, Hotmail, Outlook, iCloud, Protonmail, and more.

Parametersemailrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.