mcpbeat Sign in

emailverifier.dev MCP Server

answering

emailverifier.dev is answering right now. Last checked 2 min ago.

Verify emails and domains for routing, disposable providers, role accounts, and SMTP risk.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
304 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add emailverifier --transport http https://emailverifier.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "emailverifier": {
      "url": "https://emailverifier.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.emailverifier]
url = "https://emailverifier.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "emailverifier": {
      "url": "https://emailverifier.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "emailverifier": {
      "url": "https://emailverifier.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://emailverifier.dev/mcp streamable-http needs key 529 ms 2 min ago

Alternatives to emailverifier.dev

same job, measured the same way
Emailkind
by emailkind

Classify email addresses and domains by provider and type (business, personal, disposable).

answering
mailverdict
by mailverdict

Keyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions.

2 tools answering
Mailsink
by heocoi

Disposable inboxes for AI agents and CI: catch the verification email, read the OTP or link.

74 installs/wk local only
fixture.email — Email Testing for Agents
by fixture

Disposable test mailboxes on a real domain: send, receive and assert on real email.

answering
Temp Mail
by temp-mail

Disposable email inboxes for AI agents — read messages and verification codes.

answering
MAILTYPE — Email Domain Capability Intelligence
by gsterlingpress

Email-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS.

answering
E
Checkmails — Email Verification
by checkmails

Verify email deliverability by SMTP. Catch-all/disposable/role detection. EU-hosted, GDPR-ready.

answering
Emailfinder MCP
by xinxinhenaixin

Find verified professional emails by name, domain, LinkedIn, or role.

56 installs/wk local only

emailverifier.dev — questions

Answers built from our own checks of this server.

Why is there no tool list for emailverifier.dev?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is emailverifier.dev working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 304 ms. The bar chart above shows every period we have measured.
Is emailverifier.dev still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect emailverifier.dev?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does emailverifier.dev need an API key?
Yes. Every time we knock, emailverifier.dev answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is emailverifier.dev?
It answers our handshake in 304 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.