Verifi.Email
Verifi.Email validates email addresses and checks domain email-security configuration through its public API.
Verdict
Common use cases
- Scrub lead lists before email campaigns
- Flag disposable addresses in signup forms
- Audit sender domains during phishing investigations
- Validate customer emails before onboarding
- Check SPF and DMARC for partner domains
Integration
- Vendor
- Verifi.Email
- Category
- other
- Auth
- API_KEY
- Tools
- 3
- Composio slug
verifi_email
Tools
- Check Domain Health
Check a bare domain's SPF, DKIM, DMARC, and BIMI configuration and return protocol scores plus provider recommendations.
- Validate Email
Validate one non-empty email address and return its overall validity plus syntax, MX, spoofing, and disposable-address signals.
- Validate Emails
Validate 1-10 email address strings in one synchronous request and return one ordered result per input, including malformed strings as invalid results.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and search for Verifi.Email. 2. Click Connect and paste your Verifi.Email API key when prompted (generate one at verifi.email/dashboard under API Keys). 3. Grant read access to validation and domain-check endpoints—no write scopes exist. 4. Click Test Connection; Switchy will validate a sample address to confirm the key works. 5. Open any Project and type '@Verifi.Email validate user@example.com' in a message to invoke the validation tool. 6. The MCP returns a structured result showing overall validity, syntax status, MX record presence, spoofing risk, and whether the domain is disposable. 7. For domain audits, use '@Verifi.Email check domain health example.com' to see SPF, DKIM, DMARC, and BIMI scores plus configuration recommendations.
What teammates see: by default, memories from Verifi.Email 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
Validate Lead Batch
@Verifi.Email validate these addresses and tell me which ones are invalid or disposable: alice@example.com, bob@tempmail.net, carol@company.io
Audit Sender Domain
@Verifi.Email check domain health for suspicious-sender.com and summarize any missing or misconfigured records
Pre-Campaign Cleanup
@Verifi.Email validate these five VIP addresses and flag any that might bounce: exec1@corp.com, exec2@startup.io, exec3@agency.co
Disposable Address Check
@Verifi.Email validate newuser@10minutemail.com and tell me if it's a disposable address
Partner Domain Review
@Verifi.Email check domain health for partner-vendor.com and list any SPF or DMARC issues that could affect deliverability
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Verifi.Email validate the email address support@acme-corp.io and tell me if it's safe to send to
The address support@acme-corp.io is valid and deliverable. Syntax is correct, MX records exist and point to Google Workspace servers, no spoofing indicators detected, and it's not a disposable address. The domain has strong SPF and DMARC policies in place. Safe to add to your outreach list.
This example shows single-address validation, which is the most common use case for verifying a contact before sending. The MCP returns structured signals (syntax, MX, spoofing, disposable) that the AI synthesizes into a plain-English recommendation. Requires API key with validation quota; each check consumes one credit.
@Verifi.Email check the domain health for newclient.com — we're about to send a campaign and I want to know if their mail setup will cause deliverability issues
Domain newclient.com has partial email authentication: SPF is configured correctly (score 10/10), but DKIM is missing (score 0/10) and DMARC is set to 'none' policy (score 3/10). BIMI is not configured. Recommendation: emails sent to this domain should deliver, but replies from their domain may land in spam folders due to weak sender authentication. Consider advising them to harden DMARC before launch.
This example demonstrates the domain health check, which audits SPF, DKIM, DMARC, and BIMI configurations. Useful when onboarding a new client or partner to assess their email infrastructure risk. The MCP returns numeric scores and the AI translates those into actionable advice. No side effects; read-only operation.
@Verifi.Email validate this list of emails from our signup form: alice@example.com, bob@tempmail.net, carol@, dave@company.co.uk — flag any that look risky
Validated 4 addresses: alice@example.com is valid and deliverable. bob@tempmail.net is valid syntax but flagged as a disposable address (high risk for fraud or low engagement). carol@ is malformed and invalid. dave@company.co.uk is valid with strong MX records. Recommendation: accept alice and dave, reject carol outright, and consider blocking or quarantining bob due to disposable provider.
This example shows bulk validation (up to 10 addresses per request), which is ideal for cleaning form submissions or import lists in one pass. The MCP processes all inputs synchronously and returns per-address results, including malformed entries. The AI layers on risk interpretation (disposable = fraud signal). Each address consumes one validation credit.
Use-case deep-dives
When batch validation beats manual scrubbing for outbound teams
A 6-person sales team runs weekly cold-email campaigns and pulls leads from conference lists and LinkedIn exports. Half the bounces come from typos or dead domains, not bad targeting. The Validate Emails tool handles up to 10 addresses per call, so you can wire it into a Switchy prompt that checks each batch before import. The MX and disposable-address signals catch role accounts and burner emails that would tank your sender reputation. If your list is over 500 contacts per week, you'll hit rate limits fast and need a dedicated validation service. Below that threshold, this MCP keeps your CRM clean without a separate SaaS contract.
Why single-address validation matters for customer-facing workflows
A 3-person support team triages inbound tickets from a shared inbox and needs to flag suspicious senders before escalating to engineering. The Validate Email tool runs one address at a time and returns syntax, spoofing, and disposable flags in under two seconds. You can drop it into a Switchy agent that scans the From header and surfaces risk scores alongside the ticket summary. The spoofing check catches domain typos that slip past basic regex. If you're processing more than 50 tickets per hour, the single-address limit becomes a bottleneck and you'll want a webhook-based validator. For smaller teams doing manual triage, this MCP adds a verification layer without leaving the workspace.
When SPF and DMARC checks belong in your pre-launch checklist
A 4-person marketing team launches a new product subdomain and needs to confirm email authentication before the first campaign goes out. The Check Domain Health tool scans SPF, DKIM, DMARC, and BIMI records and returns protocol scores plus provider-specific fixes. You can wire it into a Switchy prompt that runs the audit and formats the output as a go/no-go checklist. The provider recommendations catch misconfigurations that would send your emails to spam. If you're managing more than three sending domains, you'll want a monitoring dashboard that tracks changes over time. For one-off launches or quarterly audits, this MCP gives you the technical read without a separate compliance tool.
Frequently asked
What does the Verifi.Email MCP do in Switchy?
It validates email addresses and checks domain health directly from your Switchy workspace. The MCP runs syntax checks, verifies MX records, flags disposable addresses, and audits SPF, DKIM, DMARC, and BIMI configurations. You can validate single addresses or batches of up to ten at once, making it useful for cleaning contact lists or debugging deliverability issues without leaving your AI chat.
Do I need a Verifi.Email account to use this MCP?
Yes. You need an active Verifi.Email account and an API key to authenticate the MCP in Switchy. The key is entered once during setup and stored securely. If you don't have an account, you'll need to sign up with Verifi.Email first—Switchy doesn't provide API keys or trial access on their behalf.
Can the MCP fix broken SPF or DMARC records for me?
No. The MCP only audits your domain's email authentication setup and returns protocol scores plus provider recommendations. It won't modify DNS records or apply fixes. You'll still need to log into your DNS provider to update SPF, DKIM, DMARC, or BIMI entries based on the MCP's findings.
How is this different from using Verifi.Email's dashboard directly?
The MCP brings validation and domain checks into your Switchy workspace, so you can verify addresses mid-conversation without switching tabs. It's faster for ad-hoc checks or when you're already working in Switchy. For bulk operations beyond ten addresses or historical reporting, you'll still want Verifi.Email's web dashboard.
Who on the team should connect the Verifi.Email MCP?
Anyone who manages email campaigns, cleans contact lists, or troubleshoots deliverability. Typically that's a marketing ops person or a developer handling transactional email. The API key is workspace-scoped in Switchy, so once one person connects it, the whole team can validate addresses without needing their own Verifi.Email logins.