MyEmailVerifier
MyEmailVerifier checks individual email addresses for deliverability and risk signals such as disposable, role-based, catch-all, and greylisted status.
Verdict
Common use cases
- Scrub lead lists before email campaigns
- Validate customer emails at signup
- Flag risky addresses in CRM imports
- Check bounce-prone contacts before outreach
Integration
- Vendor
- MyEmailVerifier
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
myemailverifier
Tools
- Verify Email
Verify one email address for deliverability and return MyEmailVerifier's status, diagnosis, and risk flags. Each request consumes one verification credit.
- Verify Emails
Verify 1 to 5 email addresses serially and return one ordered outcome per input. Each provider request is expected to consume one verification credit; locally invalid and unattempted items consume none.
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to Integrations, then click Add MCP Server. 2. Select MyEmailVerifier from the catalog. 3. You'll be prompted to paste your API key; retrieve it from your MyEmailVerifier account dashboard under API Access or Developer Settings. 4. Paste the key into Switchy and click Connect. 5. Switchy will test the connection by calling the vendor's health endpoint; if successful you'll see a green checkmark. 6. Open any Project and type '@MyEmailVerifier verify the email john@example.com' in a message. 7. The MCP will return a status object showing whether the address is deliverable, along with risk flags like disposable or role-based. 8. If the test works, the integration is live and your team can verify addresses in any conversation.
What teammates see: by default, memories from MyEmailVerifier 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 Address
@MyEmailVerifier verify the email address candidate@startup.io and tell me if it's safe to send to.
Batch Verify List
@MyEmailVerifier verify these emails: alice@acme.com, bob@widgets.co, carol@example.org, dave@temp-mail.net, eve@company.io. Show me which are valid.
Check Disposable Domains
@MyEmailVerifier verify test@guerrillamail.com and flag whether it's a disposable address.
Validate Role Addresses
@MyEmailVerifier check if info@business.com is a role-based address and explain the deliverability implications.
Audit CRM Import
@MyEmailVerifier I'm importing contacts from a spreadsheet. Verify these five: john@oldcorp.biz, jane@newco.io, admin@site.net, user@fake.xyz, real@verified.com.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@MyEmailVerifier verify the email address support@acme-corp.io and tell me if it's safe to send our product announcement.
MyEmailVerifier reports that support@acme-corp.io is **deliverable** with low risk. The domain has valid MX records, the mailbox exists, and no disposable or role-account flags were raised. The diagnosis indicates this is a monitored corporate inbox. This verification consumed 1 credit from your account balance.
This example shows single-address verification, the MCP's primary use case. Each verification consumes one API credit regardless of outcome, so teams should verify strategically rather than checking every address in bulk. Requires a valid API key with sufficient credit balance.
@MyEmailVerifier check these five addresses from our beta signup form: alice@example.com, bob@temp-mail.org, carol@company.net, invalid@, dave@oldstartup.io
MyEmailVerifier processed 5 addresses and returned: alice@example.com is **deliverable** (low risk), bob@temp-mail.org is **risky** (disposable domain detected), carol@company.net is **deliverable** (low risk), invalid@ is **invalid** (malformed syntax, no credit consumed), and dave@oldstartup.io is **undeliverable** (domain has no MX records). Total credits consumed: 4.
Batch verification processes up to 5 addresses per request. Locally invalid entries (malformed syntax) skip the API call and consume no credits, but deliverable, risky, and undeliverable results each cost one credit. Useful for cleaning signup lists before a campaign launch.
@MyEmailVerifier verify the three contact emails in our CRM export and draft a short memo explaining which ones we should remove before the next newsletter send.
MyEmailVerifier checked the three addresses: contact@vendor-a.com is deliverable, info@vendor-b.net is risky (role account with high bounce history), and sales@vendor-c.org is undeliverable (mailbox does not exist). **Memo**: Remove sales@vendor-c.org immediately to protect sender reputation. Consider segmenting info@vendor-b.net into a lower-priority list due to role-account risk. contact@vendor-a.com is safe to include. Total credits used: 3.
This example pairs verification data with AI reasoning to produce an actionable recommendation. The MCP returns structured risk flags (disposable, role, bounce history), which the AI interprets in context. Teams should verify addresses before high-stakes sends to avoid damaging domain reputation with hard bounces.
Use-case deep-dives
When to verify emails before a cold outreach campaign
A 3-person growth team is prepping a 400-contact cold email campaign and needs to scrub bounces before hitting send. MyEmailVerifier is the right call here if your ESP charges per send or penalizes bounce rates above 5%. The MCP's single-verify and batch-verify tools let you check deliverability in Switchy without leaving your campaign planning thread, and each verification consumes one credit—so you pay only for what you check. The trade-off: if you're verifying more than 1,000 emails a week, a bulk verification service with tiered pricing will cost less than per-credit APIs. For small batches where you need results in-context during planning, this MCP keeps the workflow tight and the bounce rate low.
Why this MCP matters for high-stakes support triage
A 5-person support team fields 60 tickets a day, and 15% come from throwaway or typo'd email addresses that waste follow-up cycles. MyEmailVerifier fits if you're triaging tickets in Switchy and need to flag risky senders before assigning work. The verify-email tool returns status, diagnosis, and risk flags in one call, so your team can route low-risk contacts to self-service and reserve human time for verified accounts. The boundary: if your ticketing system already has sender validation built in, adding this MCP is redundant. But if you're working across multiple inboxes or need to verify ad-hoc contacts mid-conversation, the API-key auth and two-tool scope make it fast to wire up and cheap to run at support scale.
When email verification prevents duplicate event signups
A 2-person events team is managing registration for a 200-seat webinar and suspects 20% of signups are duplicates or fake emails inflating the headcount. MyEmailVerifier is a good fit if you're building the attendee list in Switchy and need to confirm deliverability before sending calendar invites. The batch-verify tool handles up to 5 emails per call, so you can check small cohorts as registrations arrive without burning credits on bulk uploads. The limit: if your event platform already dedupes by email or you're running weekly webinars at scale, a native integration will save more time than an MCP. For one-off or quarterly events where you're coordinating across Slack, spreadsheets, and Switchy, this MCP keeps the list clean without adding another SaaS login.
Frequently asked
What does the MyEmailVerifier MCP do in Switchy?
It checks whether email addresses are real and deliverable before you send. The MCP exposes two tools: one verifies a single address, the other verifies up to five at once. Each verification consumes one credit from your MyEmailVerifier account. Use it to clean contact lists, validate form submissions, or filter bounces before a campaign.
Do I need a MyEmailVerifier account to use this MCP?
Yes. You need an active MyEmailVerifier account and an API key. Paste the key into Switchy's connection screen and the MCP will authenticate. Every verification call deducts credits from your MyEmailVerifier balance, so make sure you have enough before running batch checks.
Can the MCP verify email addresses in bulk?
Sort of. The batch tool verifies up to five addresses per call, processing them serially. If you need to verify hundreds or thousands, you'll either run the tool repeatedly or use MyEmailVerifier's web dashboard for true bulk uploads. The MCP is best for on-demand checks during conversations, not mass list hygiene.
How is this different from checking emails manually on MyEmailVerifier's site?
The MCP lets your AI assistant verify addresses mid-conversation without leaving Switchy. Instead of copying emails to a browser tab, you ask the assistant to check them and it returns status, diagnosis, and risk flags inline. Same underlying service, faster workflow when you're already working in Switchy.
Who on the team should connect this MCP?
Whoever owns your MyEmailVerifier account and API key. That person connects it once in Switchy, then everyone in the workspace can ask the assistant to verify emails. Just remember: every verification burns a credit from the shared MyEmailVerifier balance, so set expectations with the team.