NeverBounce

@NeverBounce check my account credits and show me how many verification jobs I've run this month

Your NeverBounce account currently has 14,732 credits remaining. This month you've completed 8 bulk verification jobs, processing a total of 42,150 email addresses. Your account tier is Professional, with a monthly credit allocation of 50,000. Based on current usage, you're on track to use approximately 60% of your monthly credits. The last job completed 3 days ago verified 6,200 addresses with a 12% bounce rate.

This example demonstrates read-only account monitoring. The MCP retrieves usage statistics without modifying anything. Useful for budget tracking before launching large verification jobs. Requires valid API key with account read permissions.

@NeverBounce start a bulk verification job for the CSV file I just uploaded, enable auto-parsing and send results to our webhook when done

Bulk verification job created successfully. Job ID: 3847291. NeverBounce is now processing your uploaded CSV with auto-parsing enabled to detect email columns automatically. The job contains 8,450 email addresses and is currently in 'parsing' status. Estimated completion time is 12-15 minutes based on current queue load. Results will be posted to your configured webhook endpoint (https://yourapp.com/neverbounce-callback) when verification completes. You can check progress with the job ID.

This example shows asynchronous job creation with callback configuration. The MCP initiates verification but doesn't wait for completion—results arrive via webhook. Be aware this consumes account credits immediately (one credit per email). Job deletion is irreversible if you need to cancel.

@NeverBounce get the status of job 3847291 and if it's done, summarize the verification results by email validity category

Job 3847291 completed 4 minutes ago. Here's the breakdown of 8,450 verified addresses: Valid (deliverable): 7,102 emails (84.0%)—these are safe to send to. Invalid (bounce risk): 891 emails (10.5%)—hard bounces, remove these immediately. Catchall: 312 emails (3.7%)—accept-all domains, moderate risk. Unknown: 145 emails (1.7%)—verification inconclusive, often due to temporary server issues. The job processed in 11 minutes and consumed 8,450 credits. You can now download the segmented CSV to update your mailing list and remove the invalid addresses before your next campaign.

This example pairs the MCP's status-check tool with AI reasoning to interpret verification categories. The summary helps non-technical users understand bounce risk without reading raw API responses. Requires the job to be complete; polling incomplete jobs returns progress percentages instead of results.

When to verify your list before a product launch email

A 6-person marketing team is prepping a product launch email to 18,000 leads scraped from conference sign-ups and webinar registrations. NeverBounce is the right call here if you're sending cold or aged lists where bounce rate kills deliverability. Create a bulk verification job with the list CSV, wait 10-30 minutes depending on size, then download the segmented results to strip out invalid addresses before you hit send. The break-even is around 2% expected bounce rate—below that, you're paying for verification you don't need. Above 5%, skipping verification tanks your sender reputation and costs more in the long run. If your team sends fewer than 3 campaigns a year, the per-credit cost adds up; consider a pay-as-you-go plan and verify only your top-funnel segments.

Using NeverBounce to clean a stale Salesforce export

A 3-person sales ops team inherits a Salesforce instance with 40,000 contacts, half of which haven't been touched in two years. NeverBounce works if you need a one-time scrub before migrating to a new CRM or re-engaging dormant accounts. Export the contact list, run a bulk job, then use the results CSV to flag or delete invalid records in Salesforce. The job status tool lets you poll progress without blocking your workflow. The trade-off: NeverBounce charges per email verified, so a 40k audit costs real money—budget around $200-400 depending on your plan. If you're cleaning lists quarterly or more, look at real-time verification at the point of capture instead. For a one-off audit where you need confidence before a big re-engagement push, this MCP gets the job done in an afternoon.

When real-time verification beats bulk jobs for lead quality

A 4-person growth team runs a SaaS trial signup form that converts 200 leads a week. NeverBounce's JS widget event tool is built for this: verify emails at the point of entry, reject obvious typos or disposable addresses before the lead hits your CRM. The widget sends form load and completion events, so you can track verification coverage and catch integration issues early. This scenario only makes sense if your cost-per-lead is high enough to justify the per-verification fee—think enterprise SaaS, not consumer apps. If you're converting thousands of signups daily, the API call overhead and cost per email verified will hurt. But for a team where every qualified lead matters and you're already paying for email verification somewhere in the funnel, wiring this MCP into your signup flow cuts junk leads at the source and keeps your nurture sequences clean from day one.