Bouncer

@Bouncer verify the domain example.com and check if it has proper MX records and catch-all configuration

Domain verification complete for example.com. The domain has valid MX records pointing to mail.example.com (priority 10) and backup.example.com (priority 20). Catch-all behavior: disabled — the server rejects invalid addresses at SMTP time. DNS configuration appears healthy with no obvious deliverability issues. This domain is suitable for email verification workflows.

This example shows domain-level validation, useful before verifying individual addresses. Note that domain verification doesn't guarantee individual email deliverability — it only confirms infrastructure setup. Requires API key with domain verification scope.

@Bouncer create a batch verification request for these 50 support@ addresses from our CRM export, then check the status every 30 seconds until complete

Batch request created with ID batch_7x9k2m. Initial status: processing. Polling status... After 90 seconds, batch completed with 50/50 emails verified. Results summary: 42 deliverable, 5 undeliverable (invalid mailbox), 3 risky (disposable domains detected). You can retrieve full results using the batch ID or delete the batch to reclaim unused credits if verification stopped early.

This example demonstrates batch processing with status polling — the typical workflow for verifying lists. Batch jobs are asynchronous; larger lists take longer. The MCP handles polling logic, but you're responsible for deciding when to call 'Finish Batch' to stop processing and recover credits for unverified emails.

@Bouncer run a toxicity analysis on our newsletter subscriber list and summarize which addresses are spam traps or known complainers

Toxicity list job created (job ID: tox_4p8n1q) and completed after 45 seconds. Analyzed 200 addresses. Findings: 8 addresses flagged as spam traps (4%), 3 identified as known complainers based on historical abuse reports, 189 clean. High-risk addresses include disposable domains like tempmail.org and guerrillamail.com. Recommend removing flagged addresses before your next campaign to protect sender reputation.

Toxicity analysis goes beyond deliverability — it identifies addresses that could harm sender reputation even if technically valid. This is a separate job type from standard verification. Results depend on Bouncer's threat intelligence database. Use this before bulk email sends, not for real-time signup validation.

When Bouncer wins for cleaning trial signups at scale

A 6-person SaaS team sees 200+ trial signups weekly, but 30% are disposable emails or typos that never convert. Bouncer's batch verification tools let you run nightly jobs against new signups, flagging toxic addresses before they hit your CRM or trigger onboarding emails. The toxicity list job handles the heavy lift—create the job, poll status, retrieve results—while domain verification catches catch-all servers that bloat your list. This works best when your signup volume justifies the API overhead (under 50 signups/day, manual review is faster). If you're already piping signups through Zapier or n8n, Bouncer slots in as a pre-filter step. The buying call: you need this if bad emails are skewing your activation metrics or costing you send credits.

Why Bouncer matters for support ticket routing

A 3-person support team gets 40 inbound emails daily, but 15% are from invalid addresses that can't receive replies. Bouncer's single-email verification (implied by batch tools) lets you check sender validity before creating a ticket, routing bad addresses to a dead-letter queue instead of wasting agent time. The domain verification tool confirms whether the sender's domain is misconfigured, which helps you decide if it's a typo or a systemic issue. This scenario breaks down if your support volume is under 10 emails/day—manual spot-checks are cheaper. It also assumes you're not using a helpdesk that already validates senders (Zendesk does this natively). The call: adopt Bouncer if reply failures are creating follow-up loops that burn agent hours.

When batch toxicity checks save deliverability

A 2-person content team maintains a 12,000-subscriber newsletter but hasn't cleaned the list in 18 months. Bouncer's batch request and toxicity job tools let you upload the full list, flag disposable or abusive addresses, and delete the batch after export—all without manual CSV wrangling. The 9-tool limit means you're running a linear workflow (create batch, poll status, get results, finish batch, delete job), which is fine for quarterly audits but clunky for real-time validation. This wins when your list is large enough that bounce rates hurt sender reputation (over 5,000 subscribers) but small enough that batch processing finishes in minutes. The threshold: if you're sending daily and need sub-second validation, Bouncer's batch model is too slow. Use this for scheduled cleanups, not live sends.