Verifiedemail
VerifiedEmail offers real-time email verification and bulk email list cleaning services to ensure the accuracy and deliverability of email communications.
Verdict
Common use cases
- Scrub imported contact lists for bad emails
- Validate form submissions before saving to CRM
- Audit user tables for undeliverable addresses
- Check bulk file uploads for bounce risk
- Retrieve 1-click signup credentials after verification
Integration
- Vendor
- Verifiedemail
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
verifiedemail
Tools
- Check Credits
Tool to retrieve the remaining verification credits. use after confirming account authentication to ensure you have sufficient credits before performing verification operations.
- Check File Status
Tool to check the status of a previously uploaded file. use after uploading a file when polling for verification progress.
- Get 1-Click User Data
Tool to retrieve data for a user who has completed a 1-click signup flow. use after you have the identityuuid to fetch the verified user's full profile.
- Get Shared Credentials
Tool to retrieve a list of shared credential ids. use when you need to fetch all credentials shared to your account after authentication.
- Get Shared Credentials
Tool to retrieve verified credential data shared by a user. use after obtaining a list of credential ids to fetch their details.
- Update 1-Click Credentials
Tool to update 1-click credentials. use after obtaining a 1-click session uuid when you need to update user-provided credential values in a non-hosted or trusted flow.
- Verify Email
Tool to verify the deliverability and validity of an email address. use when you need to confirm if an email can receive mail by checking server existence, mailbox status, and more.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Click 'Add MCP Server' and select Verifiedemail from the list. 3. Go to your Verifiedemail dashboard, generate an API key under Account > API Access, and copy it. 4. Paste the API key into the Switchy connection form and click 'Connect'. 5. Switchy will confirm the connection and display 'Verifiedemail ready' in the integrations list. 6. Open any Space, type '@Verifiedemail check credits' in the chat, and send — the MCP should return your remaining verification balance. 7. To verify an email, type '@Verifiedemail verify email address@example.com' and the tool will report deliverability status, mailbox validity, and any detected issues.
What teammates see: by default, memories from Verifiedemail are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Verify Single Email
@Verifiedemail verify the email address support@example.com and tell me if it's deliverable, including any warnings about the mailbox or domain.Open in a Space →
Check Credit Balance
@Verifiedemail check how many verification credits I have left in my account right now.Open in a Space →
Audit Contact List
@Verifiedemail verify these three emails: alice@company.com, bob@oldomain.net, charlie@startup.io — report which ones are safe to send to and which will bounce.Open in a Space →
Check File Status
@Verifiedemail check the status of file ID 12345 that I uploaded yesterday for bulk verification.Open in a Space →
Retrieve Shared Credentials
@Verifiedemail get the list of shared credential IDs for my account, then retrieve the full data for credential ID abc-xyz-789.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@verifiedemail verify the email address support@example-startup.com and tell me if it's safe to add to our mailing list
The email support@example-startup.com passed verification checks. The domain has valid MX records, the mailbox exists and can receive mail, and no disposable email patterns were detected. Deliverability score: 95/100. Safe to add to your mailing list. Note: This is an illustrative example—actual verification results depend on the target mail server's configuration and response at query time.
This example highlights the core email verification workflow. Before running bulk verifications, use the Check Credits tool to confirm you have sufficient API credits. Each verification consumes one credit, so monitor usage if processing large lists.
@verifiedemail I uploaded a CSV of 500 email addresses an hour ago as file ID abc123. What's the status of that verification job?
File abc123 status: Processing complete. 500 emails verified. Results breakdown: 412 valid, 63 invalid (mailbox does not exist), 18 risky (disposable domains), 7 unknown (mail server timeout). You can download the full results CSV from your Verifiedemail dashboard. This is an illustrative example—actual file processing times vary by queue load and file size.
Batch verification via file upload is asynchronous. Use Check File Status to poll progress rather than blocking on a single request. Large files (1,000+ rows) may take several minutes to process, so design your workflow to handle delayed results.
@verifiedemail retrieve the shared credentials for identity UUID xyz789 and summarize what information the user verified during signup
User xyz789 completed 1-click signup and shared verified credentials: email (john.doe@company.com, verified via inbox challenge), phone (+1-555-0199, verified via SMS code), and LinkedIn profile (linkedin.com/in/johndoe, OAuth-confirmed). All credentials passed verification on 2025-01-15. This is an illustrative example—actual shared data depends on what the user consented to share during the 1-click flow.
This example demonstrates the 1-click user data retrieval flow, useful for onboarding or KYC workflows. The MCP requires the identityuuid from your application's signup callback. Shared credentials respect user consent—only data the user explicitly authorized will be returned.
Use-case deep-dives
When batch email verification saves your sender reputation
A 6-person marketing team at a B2B SaaS company imports 3,000 leads from a trade show spreadsheet. Before loading them into HubSpot, they run the list through this MCP's Verify Email tool in a Switchy workflow. The tool catches 400 invalid addresses (typos, defunct domains, role accounts) and flags 200 catch-alls. The team drops the invalids and segments the catch-alls for a separate nurture track. This takes 15 minutes and costs $12 in credits. The alternative—sending to unverified addresses—risks a spam complaint spike that tanks their domain reputation for months. If your list is under 5,000 contacts and you send fewer than twice a month, this MCP is the right call. Over that threshold, you need a dedicated email hygiene platform with real-time API hooks.
Why real-time email verification stops fake trial accounts
A 3-person product team at a fintech startup sees 30% of trial signups never activate. They suspect disposable email abuse. They wire this MCP's Verify Email tool into their Switchy onboarding agent: when a user submits an email, the agent checks deliverability and flags disposable domains before creating the account. Over two weeks, they block 120 throwaway addresses and see activation rates climb to 48%. The Check Credits tool runs every morning to confirm they have budget for the day's signups. This works because their trial volume is under 500 per week. If you're onboarding 2,000+ users daily, you need a verification service with sub-200ms latency and a CDN—this MCP's API won't keep up with that scale.
When shared credential lookup routes high-value support faster
A 5-person support team at a healthcare SaaS company uses a 1-click signup flow for patient portals. When a ticket comes in, the agent pastes the user's email into a Switchy prompt. The MCP's Get 1-Click User Data tool pulls the verified profile (name, phone, insurance ID) from the identityuuid tied to that email. The agent routes the ticket to the correct care coordinator in 30 seconds instead of 4 minutes of back-and-forth. This MCP is the right fit because the team handles 40-60 tickets daily and the 1-click flow already exists. If your support volume is over 200 tickets per day or you don't use a 1-click identity system, you're better off with a CRM integration that surfaces customer data natively in your helpdesk.
Frequently asked
What does the Verifiedemail MCP do in Switchy?
It verifies email deliverability and validates user credentials through your Verifiedemail account. The MCP checks if email addresses can receive mail, retrieves shared credential data from users who've completed verification flows, and monitors your remaining verification credits. You can verify individual emails or check the status of bulk file uploads.
Do I need a paid Verifiedemail account to use this MCP?
Yes. You need an active Verifiedemail account with an API key and available verification credits. The MCP checks your credit balance before running verifications, so if you're out of credits, verification requests will fail. Connect the MCP using your API key from the Verifiedemail dashboard.
Can this MCP verify emails in real-time during signup flows?
Yes, but with caveats. The Verify Email tool checks deliverability by pinging mail servers, which takes 2-5 seconds per address. For real-time signup validation, you'll want to call it before account creation. For bulk verification of existing lists, use the file upload tools and poll status instead of verifying one-by-one.
How is this different from using Verifiedemail's API directly?
The MCP wraps Verifiedemail's API so your AI agents can verify emails and retrieve credential data without you writing integration code. If you're already calling the Verifiedemail API from your app, this adds no value. It's useful when you want Claude or another AI to handle verification logic as part of a larger workflow.
Who on the team should connect this MCP?
Whoever manages your Verifiedemail account and has access to the API key. Since verifications consume credits that cost money, you probably don't want every team member triggering verifications. Connect it to a shared Switchy workspace where only authorized people can run verification workflows.