Dilli Email Validation Api Server

com.dillilabs.devaPublished by deva.dillilabs.comOfficial publisherv1.0.1Updated Oct 27, 2026

An MCP server that provides tools to validate an email address using Dilli Email Validation API.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant validate a single email address through the Dilli Email Validation (DEVA) API.

What you can do
Validate email addresses: check a given address through the DEVA API and return the validation result.
When to use it
Useful when an assistant needs to check whether an email address is valid, for example before storing, sending to, or signing up with it.
Requirements
A remote endpoint at deva.dillilabs.com over streamable HTTP. An API key is required and sent in the X-DEVA-API-Key header; the key can be obtained by registering on the provider's site.
Before you install
The API key is a secret sent in the X-DEVA-API-Key header, so keep it out of logs and shared transcripts. Email addresses submitted for validation are sent to the third-party DEVA service.

Installation

In SourceWeft

  1. Open Dilli Email Validation Api Server in the dashboard and add it to a workspace.
  2. Connect X-DEVA-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.dillilabs.deva%2Fdilli-email-validation-api-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dilli-email-validation-api": {
      "type": "http",
      "url": "https://deva.dillilabs.com/mcp",
      "headers": {
        "X-DEVA-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

1

validate_email

Validates an email address using the DEVA API.

Parametersemailrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.