MCP QUEEN
dev.mailverdict/mailverdict A
Keyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions.
Communicationv0.1.1streamable-httpapi.mailverdict.dev repository
Grade evidence — probed 2026-07-13 10:30 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 140ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo mailverdict@0.1.1 |
| tooling | 35 / 35 | tools/list OK: 2 tools e.g. "check_email"; 2/2 described, 2/2 fully-typed schemas, median description 219 chars |
| latency | 10 / 10 | initialize round-trip 140ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.1; namespace dev.mailverdict matches endpoint/repo |
Score 100/100 · latency 140ms · 2 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http mailverdict https://api.mailverdict.dev/mcp
Generic MCP client config:
{ "mcpServers": { "mailverdict": { "type": "http", "url": "https://api.mailverdict.dev/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/dev.mailverdict/mailverdict · referral link https://mcpqueen.com/go/dev.mailverdict/mailverdict (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/dev.mailverdict/mailverdict)
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.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 10:30 | A | 100 | 140ms |