NeverBounce
NeverBounce provides email verification services to ensure the validity of email addresses, enhancing deliverability and reducing bounce rates.
Verdict
Common use cases
- Scrub email lists before campaign launch
- Validate signups at registration in real time
- Audit CRM contacts for deliverability risk
- Segment invalid addresses from good ones
- Monitor verification credit usage across team
Integration
- Vendor
- NeverBounce
- Category
- other
- Auth
- API_KEY
- Tools
- 12
- Composio slug
neverbounce
Tools
- Create NeverBounce Bulk Verification Job
Tool to create a new bulk verification job with parsing, sampling, and callback options. use for asynchronous list verification with advanced control.
- Delete NeverBounce Jobdestructive
Tool to permanently delete a job and its results. use when you need to irreversibly remove a bulk verification job. this delete is irreversible.
- Delete NeverBounce Jobdestructive
Tool to permanently delete a job and its results. use when you need to irreversibly remove a bulk verification job. deletion is irreversible.
- Download Job Results (GET)
Tool to download job results as a csv file via get. use after job completion to retrieve segmented or enriched csv output.
- Download Job Results (POST)
Tool to download job results as a csv file via post. use after job completion to fetch segmented or enriched csv output.
- Get Account Info
Tool to get account information including credits, job counts, and usage statistics. use when retrieving neverbounce account summary after authentication.
- Get bulk job status
Tool to get the status and progress of a bulk verification job. use when
- JS Widget Send Event
Tool to send widget form events via the js widget api. use when reporting form.load or form.completion events after user interactions with your form.
- NeverBounce Account Info
Tool to get account information including credits, job counts, and usage statistics. use after authenticating to retrieve neverbounce account summary.
- NeverBounce Single Check
Tool to verify a single email address and gather additional information. use when you need real-time validation at the point of entry.
- Retrieve Job Results
Tool to retrieve paginated results for a completed job, including original data and verification outcomes. use after confirming job completion and when paging through results.
- Start NeverBounce Job
Tool to start a parsed job when auto start is disabled. use after creating a job with auto start=false.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to Integrations. 2. Search for NeverBounce and click Connect. 3. Log into your NeverBounce account, go to Settings > API, and copy your API key. 4. Paste the key into Switchy's prompt and click Authorize. 5. Switchy confirms the connection by fetching your account info (credits remaining, job count). 6. Open any Project, type '@NeverBounce check the validity of hello@example.com' and send. 7. The MCP returns a verification result (valid, invalid, disposable, unknown) in seconds. 8. For bulk jobs, upload a CSV to your Project files, then prompt '@NeverBounce create a bulk job from leads.csv' — the MCP starts the job and returns a job ID you can poll for status.
What teammates see: by default, memories from NeverBounce are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Verify Single Email
@NeverBounce verify the email address john.doe@company.com and tell me if it's valid, invalid, or disposable.
Bulk Job from CSV
@NeverBounce create a bulk verification job from the file contacts_export.csv I just uploaded. Enable auto-parsing and let me know the job ID.
Check Job Status
@NeverBounce get the status of bulk job ID 987654. Show me the percentage complete and any error counts.
Download Verified Results
@NeverBounce download the results for job ID 987654 as a CSV. Include only valid and catch-all addresses in the output.
Account Credit Check
@NeverBounce show me my account info including credits remaining, total jobs run this month, and any usage warnings.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@NeverBounce check the status of my bulk verification job ID 4782931 and tell me how many emails are still processing
Job 4782931 is 68% complete. Of the 15,000 emails submitted, 10,200 have been verified so far. The job is currently processing at approximately 450 emails per minute. Based on current progress, the remaining 4,800 emails should complete in about 11 minutes. So far, 8,340 emails are valid, 1,120 are invalid, and 740 are marked as risky or unknown. The job was started 23 minutes ago and has not encountered any errors.
This example shows real-time job monitoring. The MCP returns progress metrics and completion estimates, but actual processing speed varies by account tier and NeverBounce's current load. Jobs can stall or slow down unpredictably, so don't rely on ETA for time-sensitive workflows.
@NeverBounce create a new bulk verification job from my uploaded CSV 'newsletter_subscribers_march.csv' with auto-parse enabled and email me when it's done
Bulk verification job created successfully. Job ID: 4783104. The system has detected 22,340 email addresses in 'newsletter_subscribers_march.csv' and will begin processing immediately. Auto-parse is enabled, so the tool will attempt to identify the email column automatically. A callback notification will be sent to your registered email address upon completion. Estimated completion time is 45-60 minutes. This job will consume approximately 22,340 credits from your account balance.
This demonstrates asynchronous job creation with callback notifications. The MCP requires sufficient account credits before job submission—if your balance is too low, the job will fail immediately. The auto-parse feature works best with standard CSV formats; complex or multi-column files may need manual column mapping.
@NeverBounce show me my account summary including remaining credits and how many jobs I've run this month
Your NeverBounce account currently has 487,230 verification credits remaining. This month, you've completed 14 bulk verification jobs totaling 318,450 email verifications. Your account tier is 'Professional' with a monthly allowance of 500,000 credits, which resets in 9 days. Average job size this month: 22,746 emails. You have 3 jobs currently in progress and 2 jobs queued. No billing issues or account warnings are present.
This read-only example retrieves account-level metadata. The MCP only shows data visible to your API key's permission scope—team accounts may have restricted visibility. Credit counts update in real-time, but monthly usage statistics can lag by up to 15 minutes during high-traffic periods.
Use-case deep-dives
When NeverBounce saves deliverability before a product launch
A 6-person SaaS team is sending a feature announcement to 12,000 leads scraped from conference signups and webinar forms. They run a bulk verification job two days before send, segmenting out hard bounces and catch-alls. The MCP's 12 tools handle the full workflow: create the job with sampling options, poll status until complete, download the cleaned CSV, then delete the job to free credits. This works when your list is under 50k rows and you send campaigns monthly or less. If you're verifying lists daily or need real-time validation at form submission, the JS widget event tool is the better path. The buying call: use this MCP when you batch-verify before sends and want the cleanup scripted into your pre-flight checklist.
Why this MCP is overkill for ongoing CRM maintenance
A 3-person sales ops team at a B2B startup wants to clean 8,000 Salesforce contacts accumulated over two years. They export to CSV, run a NeverBounce bulk job, and re-import the valid subset. The MCP handles this one-time purge fine, but the scenario breaks down if they need continuous validation. NeverBounce charges per verification, so running weekly jobs on the same contacts burns credits fast. The account info tool shows usage stats, but there's no incremental-only mode. If your CRM grows by 200+ contacts monthly and you want automatic hygiene, you need a native Salesforce or HubSpot integration, not an MCP. The call: use this for annual purges or list imports, not for live CRM hygiene.
When bulk verification unblocks a support backlog sprint
A 5-person support team inherits 3,000 unresolved tickets after a product pivot. Half the submitter emails are typos or disposable addresses from free-trial abuse. They export the ticket list, verify in bulk, and route valid emails to follow-up while archiving the junk. The MCP's delete-job tool matters here because they're running multiple segmented jobs (one per product line) and need to clear results between runs to avoid credit waste. This scenario works when the backlog is static and you're triaging once. If tickets arrive in real-time and you need per-submission validation, the form event tool is the right hook, but that requires frontend integration. The call: use this MCP for backlog sprints, not for live ticket intake.
Frequently asked
What does the NeverBounce MCP do in Switchy?
It verifies email addresses in bulk or individually through NeverBounce's validation API. Your team can create verification jobs, check their status, download results as CSV, and monitor account credits—all without leaving Switchy. You authenticate once with your NeverBounce API key, then any workspace member can trigger validations through prompts or workflows.
Do I need admin access to connect NeverBounce?
You need a NeverBounce API key, which any account holder can generate from their dashboard. No special admin role is required. The key grants full access to your NeverBounce account's verification credits and job history, so treat it like a password. Only connect it in Switchy workspaces where you trust all members.
Can the MCP verify emails in real-time during a conversation?
Yes, but only for single-address checks. The MCP includes tools for bulk jobs (asynchronous, returns a job ID you poll later) and likely a single-verify endpoint for immediate results. Bulk jobs take minutes to hours depending on list size, so real-time validation works best for one-off checks during a chat, not for verifying thousands of addresses mid-conversation.
How is this different from calling NeverBounce's API directly?
The MCP wraps NeverBounce's REST API so Claude can call it without you writing code. If your team already has scripts or Zapier flows hitting NeverBounce, this won't replace them—it's for ad-hoc validation requests in natural language. You still burn the same NeverBounce credits per verification; Switchy just makes the API conversational.
Does running verifications count against my Switchy plan limits?
No. Verifications consume your NeverBounce account credits, not Switchy message quotas. The MCP calls themselves count as tool uses in Switchy (one per API request), but those are effectively unlimited on paid plans. Your bottleneck is NeverBounce's credit balance, not Switchy's infrastructure.