Zerobounce

@zerobounce validate these 15 email addresses from our signup form and flag any that are disposable or invalid

Validated 15 addresses in 1.2 seconds. Results: 11 valid, 2 invalid (syntax errors), 2 disposable (temporary email providers detected). The two disposable addresses are from 'tempmail.com' and 'guerrillamail.com'. All valid addresses passed SMTP and DNS checks. Activity data shows 7 of the valid addresses have recent engagement history. Full breakdown includes deliverability scores and suggested actions for each address.

Batch validation is limited to 200 emails per request and consumes credits per email checked. This example demonstrates real-time validation with activity data enabled — useful for cleaning signup lists before sending campaigns. Requires API key with validation permissions. Disposable detection helps avoid wasted sends to temporary inboxes.

@zerobounce add the domain 'competitor-company.com' to our blocklist so we stop validating their addresses

Successfully added 'competitor-company.com' to your account blocklist. Future validation requests for any email ending in '@competitor-company.com' will return a 'do_not_mail' status without consuming validation credits. Current blocklist now contains 8 domains. To remove this domain later, use the blocklist management tool with the delete action.

Allowlist and blocklist management lets you override validation logic for specific domains — useful for excluding competitors, partners, or known-bad providers. Changes apply immediately to all subsequent validation calls. This is a write operation that modifies account-level configuration, so use cautiously in shared team environments.

@zerobounce score the email 'sarah.chen@startup.io' and tell me if it's worth including in our outbound campaign

AI scoring for 'sarah.chen@startup.io': Quality score 8.2/10 (high). Analysis indicates this is likely a real person at a legitimate business domain. The address shows moderate engagement history and passed all deliverability checks. Domain 'startup.io' has valid MX records and no spam reputation flags. Recommendation: Include in outbound campaign. Note that AI scoring provides a predictive quality assessment beyond basic validation — useful for prioritizing leads before cold outreach.

AI scoring goes beyond syntax/DNS validation to predict whether an address represents a valuable lead. This example shows how to combine scoring with campaign planning decisions. Scoring consumes additional credits beyond standard validation. Best used for high-value outreach where lead quality matters more than volume. Results are probabilistic, not guaranteed.

When batch validation saves your sender reputation before a campaign

A 6-person sales team at a B2B SaaS startup scrapes 800 leads from a conference attendee list and needs to send cold emails within 48 hours. Use the Batch Validate Emails tool to check all 800 addresses in four API calls (200 per batch) before importing to your CRM. This catches role accounts, disposable domains, and typos that would otherwise tank your deliverability score. The AI Scoring tool adds a second pass for the top 200 prospects, flagging low-engagement addresses so your SDRs focus on verified contacts. If your list exceeds 5,000 emails or you run campaigns weekly, the file-based validation tools (Delete file, Domain Search Send File) handle the volume without rate-limit headaches. This MCP is overkill for one-off manual checks but essential when your outbound motion depends on list quality at scale.

Why real-time scoring matters for inbound lead qualification

A 3-person customer success team at a freemium product gets 40 support emails daily, half from free users with throwaway addresses. Wire the AI Scoring Single Email tool into your ticketing webhook so every inbound sender gets scored on arrival. High-scoring emails route to your paid-tier queue; low scores trigger an auto-reply asking for a work email. The Allow or Block List tool lets you whitelist your enterprise customers' domains and blocklist known spam sources without touching code. This setup works when your inbound volume is under 200 emails per day and you need instant triage. Above that threshold, the per-request latency adds up and you should batch-validate overnight instead. If your support flow already has strong spam filters, this MCP adds marginal value—but if you're drowning in fake signups, it pays for itself in saved CS hours.

When domain search finds hiring managers faster than LinkedIn scraping

A 2-person recruiting agency sources 300 target companies per month and needs verified contact emails for hiring managers. Upload your company domain list (one CSV with 300 rows) using Domain Search Send File, poll the status with Domain Search File Status, then download results with Domain Search Get File. This bulk workflow surfaces multiple contacts per domain—useful when you're cold-pitching and need backups if the first email bounces. The file-based tools handle the async job queue so you're not burning API calls in a loop. If you're sourcing fewer than 50 companies per month, the manual lookup overhead isn't worth the API key—just use a browser extension. But when your pipeline depends on verified emails at recruiting agency scale, this MCP turns a 4-hour manual task into a 20-minute file upload.