Emailvalidation
Validate individual email addresses for deliverability and quality signals, and inspect account quota usage through emailvalidation.io's complete REST API surface.
Verdict
Common use cases
- Verify signup emails before onboarding
- Clean CRM contact lists in bulk
- Audit disposable addresses in campaigns
- Check domain health during outreach
- Validate leads before sales handoff
Integration
- Vendor
- Emailvalidation
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
emailvalidation
Tools
- Get Account Quota Status
Return the connected emailvalidation.io account ID and current monthly and grace credit totals, usage, and remaining balances. This status check does not consume validation credits or count against the API rate limit.
- Validate Email Address
Validate one email address and return deliverability, format, mailbox, domain, role-address, disposable-address, and quality signals. Each successful validation costs one account credit. Catch-all detection is optional, disabled by default,
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to the Integrations tab. 2. Search for Emailvalidation and click Connect. 3. You'll be prompted to paste your Emailvalidation.io API key — retrieve it from your Emailvalidation.io dashboard under Account > API Keys. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection and displays your current credit balance. 6. Open any Project and type '@Emailvalidation check my quota' to verify the MCP responds with your account status. 7. To validate an address, type '@Emailvalidation validate email@example.com' and the MCP returns deliverability, domain, and quality signals in seconds. 8. Each validation consumes one credit from your Emailvalidation.io monthly allowance.
What teammates see: by default, memories from Emailvalidation 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 Remaining Credits
@Emailvalidation show me my account quota status and remaining balance for this month.
Validate Single Address
@Emailvalidation validate the email address support@example.com and tell me if it's deliverable.
Audit Campaign List
@Emailvalidation validate these three emails: alice@test.com, bob@tempmail.net, carol@company.io. Flag any that are disposable or undeliverable.
Verify Lead Before Handoff
@Emailvalidation validate jane.doe@prospect.com and check if it's a catch-all or role address before I pass this lead to sales.
Check Domain Reputation
@Emailvalidation validate admin@newdomain.co and show me the domain health and quality signals.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Emailvalidation check if support@acme-startup.io is a valid deliverable address before I add it to our CRM
Validated support@acme-startup.io — deliverable with high confidence. Format is valid, domain has active MX records, mailbox exists and is not a catch-all. Flagged as a role address (support@), not disposable. Quality score: 92/100. This validation consumed 1 credit from your monthly quota.
This example shows the core validation workflow: checking deliverability before committing an email to your database. Each validation costs one credit, so batch-validate sparingly. Role addresses (support@, info@) are legitimate but may have lower engagement than personal inboxes.
@Emailvalidation what's my current quota status? I need to validate a list of 200 leads today
Your emailvalidation.io account (ID: acct_xyz789) has 450 credits remaining this month (out of 1,000 monthly) plus 50 grace credits available. You've used 550 credits so far. With 450 credits left, you can validate your 200-lead list and still have 250 credits for the rest of the billing cycle.
Quota checks are free and don't consume credits. Use this before bulk operations to avoid mid-run failures. Grace credits kick in after monthly quota exhaustion but may incur overage fees depending on your plan — confirm billing terms with Emailvalidation before relying on them.
@Emailvalidation verify these three signup emails and flag any disposables or catch-alls: alice@tempmail.net, bob@company.com, charlie@newdomain.xyz
Validated 3 addresses (3 credits used): alice@tempmail.net is disposable (tempmail.net is a known temporary provider) — recommend blocking. bob@company.com is deliverable, not disposable, mailbox confirmed. charlie@newdomain.xyz has valid format but domain MX records indicate catch-all behavior — deliverability uncertain, proceed with caution.
This example demonstrates filtering risky signups by checking disposable and catch-all flags in one pass. Catch-all domains accept mail for any address, so validation can't confirm the specific mailbox exists. Disposable addresses are high-churn and often used for trial abuse — your signup flow should decide whether to block them outright.
Use-case deep-dives
When to validate emails at signup vs. in bulk
A 6-person SaaS team runs paid ads to a demo-request form. Half the submissions are typos or disposable addresses that waste sales time. This MCP is the right call if you validate on submit—one API call per form, catching bad emails before they hit your CRM. The two-tool setup (validate address, check quota) keeps it simple. The trade-off: each validation costs a credit, so if you're processing thousands of leads daily, you'll burn through quota fast. If your form volume is under 500 submissions a month, this MCP pays for itself by keeping your sales pipeline clean. Over that threshold, consider a batch-validation service with tiered pricing instead.
Why this MCP works for one-off sender verification
A 4-person support team gets tickets from a shared inbox where customers sometimes mistype their reply-to address. Before escalating a ticket, the agent needs to confirm the sender email is real—not a typo that will bounce the follow-up. This MCP handles that spot-check: validate the address, see if it's a role account or disposable, then route accordingly. The quota-check tool lets the team monitor credit burn without logging into the vendor dashboard. The boundary: if you're validating every inbound ticket automatically, you're better off with an email gateway that does this upstream. But for manual verification during triage—maybe 20-30 checks a week—this MCP keeps the workflow in Switchy without adding another SaaS login.
When this MCP beats a spreadsheet export-import loop
A 3-person events team collects RSVPs through Typeform and needs to scrub the list before sending calendar invites. Exporting to CSV, uploading to a validation service, then re-importing is a 15-minute detour every time. This MCP shortens that to a Switchy prompt: paste the email list, validate in one pass, flag the disposable and malformed addresses. The two-tool limit means you can't do advanced list segmentation here—just pass/fail on deliverability. If your event list is under 200 emails and you run 2-3 events a month, this MCP saves the export hassle and keeps the workflow conversational. Beyond 500 emails per event, the credit cost and lack of bulk-processing features make a dedicated validation platform the smarter buy.
Frequently asked
What does the Emailvalidation MCP do in Switchy?
It validates email addresses in real time using emailvalidation.io's API. You can check if an address is deliverable, detect disposable or role-based addresses, and verify domain and mailbox existence. Each validation costs one credit from your emailvalidation.io account. You can also check your remaining quota without consuming credits.
Do I need an emailvalidation.io account to use this MCP?
Yes. You need an active emailvalidation.io account and an API key. Switchy doesn't provide validation credits — you're billed directly by emailvalidation.io based on your plan. Connect the MCP by pasting your API key into Switchy's integration settings. No OAuth flow required.
Can this MCP validate email lists in bulk?
No. The MCP validates one email address per request. If you need to validate hundreds of addresses, you'll trigger individual API calls for each, which is slow and burns credits quickly. For bulk validation, use emailvalidation.io's web dashboard or their dedicated bulk upload feature instead.
How is this different from just calling the emailvalidation.io API directly?
It's not fundamentally different — you're still consuming the same API and credits. The MCP wraps the API so your team can validate emails inside Switchy conversations without switching tabs or writing code. If you already have custom scripts that call the API, you probably don't need this.
Who on the team should connect this integration?
Whoever owns your emailvalidation.io account and has access to the API key. Typically that's someone in ops, marketing, or engineering. Once connected, anyone in your Switchy workspace can trigger validations, but all usage counts against the same emailvalidation.io credit pool.