io.github.lazymac2x/email-validator is an MCP server published by io.github.lazymac2x, hosted at api.lazy-mac.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including validate_email, validate_batch, check_domain, suggest_fix.
Cloudflare Workers MCP server: email-validator
160 connections through 5 shared values. Tap any node.
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).
| Parameter | Type | Description |
|---|---|---|
| email * | string | Email address to validate |
{
"name": "validate_email",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"description": "Email address to validate"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Batch validate up to 100 email addresses at once. Returns individual results plus summary stats.
| Parameter | Type | Description |
|---|---|---|
| emails * | array | Array of email addresses (max 100) |
{
"name": "validate_batch",
"description": "Batch validate up to 100 email addresses at once. Returns individual results plus summary stats.",
"inputSchema": {
"type": "object",
"required": [
"emails"
],
"properties": {
"emails": {
"type": "array",
"items": {
"type": "string"
},
"description": "Array of email addresses (max 100)"
}
}
}
}Check domain reputation: MX records, SPF, DKIM, disposable detection, A record existence, and overall reputation score.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | Domain to check (e.g. gmail.com) |
{
"name": "check_domain",
"description": "Check domain reputation: MX records, SPF, DKIM, disposable detection, A record existence, and overall reputation score.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Domain to check (e.g. gmail.com)"
}
}
}
}Detect common email typos and suggest corrections (e.g. user@gmial.com -> user@gmail.com). Covers Gmail, Yahoo, Hotmail, Outlook, iCloud, Protonmail, and more.
| Parameter | Type | Description |
|---|---|---|
| email * | string | Email address to check for typos |
{
"name": "suggest_fix",
"description": "Detect common email typos and suggest corrections (e.g. user@gmial.com -> user@gmail.com). Covers Gmail, Yahoo, Hotmail, Outlook, iCloud, Protonmail, and more.",
"inputSchema": {
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"description": "Email address to check for typos"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.