Dilli Email Validation Api

by deva.dillilabs.comcom.dillilabs.deva/dilli-email-validation-api-serverv1.0.1

How the score works

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

  • Remote endpoint

Uptime

Checked  · every day

100%from 8 days of checks

Up without downtime on 8 of 8 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 1801 ms, slowest 5% 1843 ms for the handshake and the tool list, over 30 days.

2000 ms1000 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

1 tool at the last answer.

Every day
DayResultChecksMedian
7 Nov (today)No downtime11837 ms
6 NovNo downtime1of 11804 ms
5 NovNo downtime1of 11806 ms
4 NovNo downtime1of 11801 ms
3 NovNo downtime1of 11778 ms
2 NovNo downtime1of 11805 ms
1 NovNo downtime1of 11793 ms
31 OctNo downtime11787 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.config/devin/mcp_config.json:

{
  "mcpServers": {
    "dilli-email-validation-api-server": {
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}

Replace YOUR_X_DEVA_API_KEY with your own value.

For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server `com.dillilabs.deva/dilli-email-validation-api-server`

Its page: https://plug.directory/servers/com.dillilabs.deva/dilli-email-validation-api-server

It runs on the publisher's servers; the client connects to its URL.

Ask the person for `YOUR_X_DEVA_API_KEY` and put it in place of the placeholder; never invent a value.

Use the section for the person's client.

## Claude Desktop

This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http dilli-email-validation-api-server https://deva.dillilabs.com/mcp --header 'X-DEVA-API-Key: YOUR_X_DEVA_API_KEY'
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "dilli-email-validation-api-server": {
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "dilli-email-validation-api-server": {
      "type": "http",
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "dilli-email-validation-api-server": {
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "dilli-email-validation-api-server": {
      "type": "streamableHttp",
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Continue

This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "dilli-email-validation-api-server":
    type: streamable_http
    name: "dilli-email-validation-api-server"
    enabled: true
    uri: "https://deva.dillilabs.com/mcp"
    headers: { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "dilli-email-validation-api-server": {
      "httpUrl": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Codex

Add to ~/.codex/config.toml:

```toml
[mcp_servers.dilli-email-validation-api-server]
url = "https://deva.dillilabs.com/mcp"
http_headers = { "X-DEVA-API-Key" = "YOUR_X_DEVA_API_KEY" }
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "dilli-email-validation-api-server": {
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "dilli-email-validation-api-server": {
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "dilli-email-validation-api-server": {
      "type": "streamable",
      "url": "https://deva.dillilabs.com/mcp",
      "headers": { "X-DEVA-API-Key": "YOUR_X_DEVA_API_KEY" }
    }
  }
}
```

## Augment Code

This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem