Dilli Email Validation Api Server
Wire email validation into your agent workflow while you build signup, waitlist, or billing forms so bad addresses are caught before they hit production.
Overview
Dilli Email Validation API Server is an MCP server for the Build phase that validates email addresses through the Dilli DEVA API from your agent.
What is this MCP server?
- Remote streamable-http MCP at https://deva.dillilabs.com/mcp (version 1.0.1)
- Validates email addresses via Dilli Email Validation API from agent-driven test flows
- Requires X-DEVA-API-Key header (register at https://deva.dillilabs.com/register)
- Fits pre-launch form QA and backend integration debugging without custom scripts
- Reduces bogus signups and support churn from typos and disposable inboxes
- Remote MCP endpoint https://deva.dillilabs.com/mcp (streamable-http)
- Package com.dillilabs.deva/dilli-email-validation-api-server version 1.0.1
- Authentication via required X-DEVA-API-Key header
What problem does it solve?
Builders integrating signup and auth flows cannot quickly verify whether an email is deliverable or malformed without leaving the agent to run ad-hoc API calls.
Who is it for?
Solo SaaS builders hooking up waitlists, onboarding, or CRM webhooks who want agent-assisted validation against a hosted email API.
Skip if: Bulk list hygiene at millions of rows, full marketing compliance programs, or teams that cannot use third-party email intelligence APIs.
What do I get? / Deliverables
After registration with a DEVA API key, your agent can validate addresses on demand so form and API integrations ship with fewer bad leads and bounce surprises.
- Agent-executed validation results for single or batch test emails
- Faster integration debugging notes linking MCP calls to your form handlers
- Reusable validation step in pre-ship signup checklists
Recommended MCP Servers
Journey fit
Email checks land when you integrate third-party APIs into auth and lead-capture flows during the Build phase, ahead of hardening in Ship. Integrations subphase is where MCP servers wrap external APIs—here the Dilli Email Validation API exposed as DEVA streamable HTTP tools.
How it compares
MCP API integration for validation, not an in-repo lint skill or complete auth provider.
Common Questions / FAQ
Who is Dilli Email Validation API Server for?
It is for developers building email capture in apps and agents who want Dillilabs validation tools without writing one-off HTTP clients in every session.
When should I use Dilli Email Validation API Server?
Use it while building or debugging signup, invite, or lead forms—or when your agent reviews integration code that should reject invalid addresses early.
How do I add Dilli Email Validation API Server to my agent?
Add the remote MCP URL https://deva.dillilabs.com/mcp in your client, set the X-DEVA-API-Key header with a key from https://deva.dillilabs.com/register, then enable the validation tools.