Bouncify
Bouncify verifies individual email addresses and bulk email lists and reports the account's remaining verification credits.
Verdict
Common use cases
- Scrub lead lists before email campaigns
- Validate customer emails at account signup
- Audit CRM contacts for deliverability
- Flag risky addresses in support tickets
- Schedule nightly bulk verification jobs
Integration
- Vendor
- Bouncify
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
bouncify
Tools
- Create Bulk List
Submit at least two email records for asynchronous bulk-job preparation without starting verification or consuming credits. Poll Get Bulk Job Status until the job is ready before starting verification.
- Download Bulk Results
Download selected result classes from a completed bulk-verification job as a CSV file.
- Get Bulk Job Status
Return a bulk job's preparation or verification state, progress, analysis, and result counts. Treat status as authoritative: a failed job can still have success=true.
- Get Credit Balance
Return the connected Bouncify account's remaining verification credits without consuming a credit.
- Request Bulk List Deletion
Permanently request deletion of a bulk list and its results. This operation is irreversible. Bouncify acknowledges an asynchronous or delayed deletion, so success means the request was accepted, not that the job has already disappeared.
- Start Bulk Verification (Irreversible, Consumes Credits)
Irreversibly start verification for a prepared bulk list. This consumes one verification credit per email and, after a successful start, cannot be paused, stopped, cancelled, or restarted. Check that the job is ready and sufficient credits
- Verify Email (Consumes Credit)
Verify one email address in real time. Every successful API call consumes one verification credit, including an address that Bouncify classifies as invalid syntax.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Bouncify in the MCP directory and click Connect. 3. You'll be prompted to paste your Bouncify API key — retrieve it from your Bouncify dashboard under Account > API Access. 4. Paste the key into Switchy and click Authorize; Switchy will validate the key by fetching your credit balance. 5. Once connected, open any Project and type '@Bouncify get my credit balance' to confirm the integration works. 6. To verify an email, try '@Bouncify verify test@example.com' — you'll see a real-time result and your credit count will drop by one. 7. For bulk jobs, first create a list with '@Bouncify create a bulk list' and attach a CSV of email records, then poll status until ready, then start verification with a separate command. 8. Remember: starting bulk verification is irreversible and consumes credits immediately, so double-check your list before you commit.
What teammates see: by default, memories from Bouncify 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
Check Credit Balance
@Bouncify get my current credit balance and tell me how many emails I can verify.
Verify Single Email
@Bouncify verify the email address john.doe@example.com and explain the result.
Create Bulk List
@Bouncify create a bulk list from this CSV of 500 leads and let me know when it's ready to verify.
Poll Bulk Job Status
@Bouncify check the status of bulk job ID 12345 and show me the progress and result counts.
Download Bulk Results
@Bouncify download the results for bulk job ID 12345 as a CSV with all result classes included.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@bouncify check my credit balance before I verify this list of 500 subscriber emails
Your Bouncify account currently has 12,847 verification credits remaining. Each email verification consumes one credit, so verifying 500 addresses would leave you with 12,347 credits. Note that even emails flagged as invalid syntax will consume a credit once verified.
Credit-balance checks are free and help you avoid running a bulk job that exceeds your quota. Always check balance before starting verification, since bulk jobs cannot be paused or cancelled once started — credits are consumed immediately.
@bouncify verify the email john.doe@example-domain.com and tell me if it's deliverable
Bouncify verified john.doe@example-domain.com and classified it as 'invalid' — the domain exists but the mailbox does not accept mail. This real-time verification consumed one credit from your account. You should remove this address from your mailing list to avoid bounce penalties.
Single-email verification is synchronous and instant, but consumes a credit regardless of the result. Use this for one-off checks or testing; for lists of 50+ addresses, bulk verification is more efficient and provides downloadable CSV reports.
@bouncify I uploaded 2,300 emails yesterday — check the status of that bulk job and summarize which addresses are safe to email
Your bulk job completed verification 14 minutes ago. Of 2,300 emails: 1,847 are 'deliverable' (safe to send), 312 are 'risky' (accept-all domains or temporary addresses), 98 are 'invalid' (non-existent mailboxes), and 43 are 'unknown' (verification timed out). Bouncify recommends mailing only the deliverable segment to protect your sender reputation.
Bulk jobs run asynchronously and can take minutes to hours depending on list size. The status endpoint is your source of truth — a job can report success=true even if some addresses failed verification. Download the CSV to see per-address classifications before sending.
Use-case deep-dives
When Bouncify saves a 10k-contact campaign from bounce penalties
A three-person growth team is about to send a product-launch email to 10,000 contacts scraped from conference attendees and webinar sign-ups. They use Bouncify's bulk-verification flow: upload the CSV via Create Bulk List, poll Get Bulk Job Status until preparation finishes, then Start Bulk Verification to consume credits and flag risky addresses. The MCP downloads results with Download Bulk Results and filters out invalid or catch-all domains before the send. This scenario wins when you're sending cold or aged lists and bounce rate directly affects deliverability. If your list is under 500 contacts or already double-opted-in, the credit cost and async overhead aren't worth it—just send and monitor bounces in your ESP.
Why Bouncify's single-verify tool fits payment flows
A two-person SaaS team wants to block fake emails at account creation to reduce failed payment notifications and support noise. They wire Switchy to call Verify Email during the signup API call, consuming one credit per attempt and rejecting addresses Bouncify flags as invalid syntax or disposable domains. The real-time response (under two seconds) keeps the form flow smooth. This works when signup volume is under 200 per day and the cost per verified email is cheaper than the support time spent chasing bounced invoices. Above 1,000 signups daily, the per-call credit burn gets expensive—switch to batch verification overnight or move validation client-side with a regex and disposable-domain blocklist.
When Bouncify cleans a stale contact database
A five-person sales team inherits a 30,000-row CRM export from a merger, half of which hasn't been touched in three years. They use Bouncify to verify the entire list in one bulk job, then Request Bulk List Deletion after downloading results to avoid leaving PII in Bouncify's system. The MCP checks Get Credit Balance before starting to confirm the account has enough credits, preventing a half-finished job. This scenario makes sense when the list is large enough that manual triage is impossible and old enough that a 15–20 percent invalid rate is expected. If your CRM already tracks email engagement (opens, clicks), filter by that first—Bouncify can't tell you if an address is monitored, only if it exists.
Frequently asked
What does the Bouncify MCP do in Switchy?
It verifies email addresses to catch bounces before you send. You can check single emails in real time or upload bulk lists for batch verification. Each verification consumes one Bouncify credit, so the MCP shows your remaining balance and lets you download results as CSV once a job finishes.
Do I need admin access to connect Bouncify?
You need a Bouncify API key, which any account holder can generate from their dashboard. The key grants full access to your credit balance and verification jobs, so treat it like a password. Only share it with teammates who should be able to spend credits and download results.
Can the MCP pause or cancel a bulk verification job?
No. Once you start bulk verification, Bouncify charges one credit per email and runs the job to completion. You cannot pause, stop, or restart it. The MCP forces you to confirm the list is ready before starting, because the operation is irreversible and immediately consumes credits.
Why use this instead of uploading CSVs to Bouncify directly?
The MCP lets you verify emails inside a Switchy workflow without switching tabs. You can check your credit balance, prepare lists, and download results without leaving the AI workspace. If you only verify once a month, the Bouncify web UI is simpler.
Who on the team should connect the Bouncify MCP?
Whoever manages email campaigns or lead lists. They already know how many credits you have and which result classes matter. Connecting the MCP does not count against Switchy seats, but every verification call spends a Bouncify credit, so limit access to people who understand the cost.