Email Validator
Validate waitlist and signup emails inside your agent workflow before you wire forms or import leads into your CRM.
Overview
io.github.lazymac2x/email-validator is a Validate-phase MCP server that lets your agent verify email addresses via a Cloudflare Workers remote endpoint.
What is this MCP server?
- Cloudflare Workers email-validator MCP at api.lazy-mac.com/email-validator/mcp
- Streamable-http remote transport—register URL in MCP config
- Server version 1.0.0 with source repo email-validator-api on GitHub
- Supports agent-driven checks during form and auth design conversations
- Useful before ship-phase security hardening on user input paths
- MCP server version 1.0.0
- 1 remote streamable-http MCP URL published in server manifest
- Cloudflare Workers deployment per server description
What problem does it solve?
Your waitlist and signup flows fill with typos and junk addresses because you have no quick validation hook while prototyping.
Who is it for?
Builders adding waitlists, magic-link auth, or newsletter capture who want MCP-native validation during validate and early build.
Skip if: High-volume senders who need full deliverability, bounce handling, and compliance tooling in one product—use a dedicated ESP plus webhooks.
What do I get? / Deliverables
After registering the remote MCP, your agent can validate emails during design and implementation so you trust early lead lists more.
- Agent-invokable email validation through MCP tools
- Cleaner early signup data before marketing sends
- Integration reference aligned with email-validator-api repository
Recommended MCP Servers
Journey fit
Invalid emails on a validation landing page poison conversion metrics and waste founder time on fake signups. Landing is where solo builders collect emails first—canonical placement is pre-launch list quality, not production monitoring.
How it compares
Focused email-validation MCP API, not a CRM, ESP, or generic form builder skill.
Common Questions / FAQ
Who is io.github.lazymac2x/email-validator for?
Solo builders and small teams using coding agents who need programmatic email sanity checks while building landing pages and auth flows.
When should I use io.github.lazymac2x/email-validator?
Use it when you are collecting emails on a validation landing page or designing signup APIs and want the agent to flag invalid addresses before you go live.
How do I add io.github.lazymac2x/email-validator to my agent?
Configure the remote MCP URL https://api.lazy-mac.com/email-validator/mcp as a streamable-http server in Claude Code, Cursor, or your MCP client, then reload MCP tools.