An MCP server that provides tools to validate an email address using Dilli Email Validation API.
Communicationv1.0.1streamable-httpdeva.dillilabs.com
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 763ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo Validate Email Address MCP Server@2.13.0.2 |
| tooling | 35 / 35 | tools/list OK: 1 tools e.g. "validate_email"; 1/1 described, 1/1 fully-typed schemas, median description 46 chars |
| latency | 7 / 10 | initialize round-trip 763ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.1; namespace com.dillilabs.deva matches endpoint/repo |
Score 94/100 · latency 763ms · 1 tools · auth: open
Claude Code:
claude mcp add --transport http dilli-email-validation-api-server https://deva.dillilabs.com/mcp
Generic MCP client config:
{ "mcpServers": { "dilli-email-validation-api-server": { "type": "http", "url": "https://deva.dillilabs.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.dillilabs.deva/dilli-email-validation-api-server · referral link https://mcpqueen.com/go/com.dillilabs.deva/dilli-email-validation-api-server (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.dillilabs.deva/dilli-email-validation-api-server)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 01:00 | A | 94 | 763ms |