
Bounceprotect
Validate signup and campaign emails via API-backed checks and SMTP verification from your coding agent.
Overview
Bounceprotect is a MCP server for the Grow phase that provides email validation and SMTP verification for agent-driven signup and campaign workflows.
What is this MCP server?
- Email validation and SMTP verification exposed as MCP tools
- Published npm package @bounceprotect/mcp with stdio transport (version 1.0.3)
- Documented for Claude Desktop, Cursor, and Claude Code
- Requires YOUR_API_KEY secret in MCP environment configuration
- Reduces bad addresses before they hit your ESP or product database
- Registry version 1.0.3 for npm package @bounceprotect/mcp
- Stdio transport in official server schema
- YOUR_API_KEY marked required and secret in package metadata
What problem does it solve?
Bad emails slip into forms and lists, hurting deliverability and wasting support time on bounces.
Who is it for?
Indie SaaS founders adding waitlists, trials, or newsletters who want verification inside Claude Code or Cursor.
Skip if: Products with no email capture, or teams that cannot use a third-party validation API key.
What do I get? / Deliverables
Agents and local tools can verify addresses at entry so you ship cleaner capture paths and fewer SMTP failures.
- Callable email validation and SMTP verification from the agent
- Cleaner capture logic you can embed in signup APIs or scripts
- MCP config snippet with secret API key wiring
Recommended MCP Servers
Journey fit
How it compares
API-backed email verification MCP, not a CRM or broadcast email platform.
Common Questions / FAQ
Who is Bounceprotect MCP for?
It is for builders on Claude Desktop, Cursor, or Claude Code who need programmatic email and SMTP checks while coding signup or campaign features.
When should I use Bounceprotect MCP?
Use it when you implement or harden email capture, invitation flows, or list imports during Grow lifecycle work or pre-launch form QA.
How do I add Bounceprotect MCP to my agent?
Add the stdio server for @bounceprotect/mcp, set the required YOUR_API_KEY environment variable, and restart your MCP client.