Connect Mailvett: Email Validation API for AI Agents and your agent gets 1 tool, among them validate_emails. It answers at https://mailvett.cybermax-tools.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 26 September 2026; the last check, on 9 November 2026, succeeded.
Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
validate_emails | Check up to 10 email addresses: syntax, whether the domain exists and has mail servers (MX), mail provider, disposable, role account (info@, sales@), free provider, likely typo with a suggested fix, domain age, SPF and DMARC. Returns verdic Inputs: emails |
Every block below points at https://mailvett.cybermax-tools.workers.dev/mcp. Pick your client and copy.
claude mcp add --transport http mailvett-email-validation-api-fo https://mailvett.cybermax-tools.workers.dev/mcp
{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mailvett.cybermax-tools.workers.dev/mcp"]
}
}
}{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"servers": {
"mailvett-email-validation-api-fo": {
"type": "http",
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"context_servers": {
"mailvett-email-validation-api-fo": {
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"serverUrl": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}name: Mailvett: Email Validation API for AI Agents
version: 0.0.1
schema: v1
mcpServers:
- name: Mailvett: Email Validation API for AI Agents
type: streamable-http
url: https://mailvett.cybermax-tools.workers.dev/mcp{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"httpUrl": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"type": "http",
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}{
"mcpServers": {
"mailvett-email-validation-api-fo": {
"url": "https://mailvett.cybermax-tools.workers.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmailvett.cybermax-tools.workers.dev%2Fmcp&type=streamable_http&id=mailvett-email-validation-api-fo&name=Mailvett%3A%20Email%20Validation%20API%20for%20AI%20Agents
It answered our last check on 9 November 2026 in 143 ms. Over 4 checks since 26 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
1, as returned by the server's own tools/list on 16 November 2026: validate_emails.
It answered our last check on 9 November 2026 in 143 ms. Over 4 checks since 26 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mailvett.cybermax-tools.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.shawmena-dotcom. Endpoint host: mailvett.cybermax-tools.workers.dev. ARD identifier: urn:air:io.github.shawmena-dotcom:mcp:email-validate.
First indexed 25 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.