Mailvett: Email Validation API for AI Agents

Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~193Tokens (tool definitions)
~648 BTypical response size
Minimal attention impact (0.15% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "email-validate": {
      "url": "https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}

Remote endpoints

https://mailvett.cybermax-tools.workers.dev/mcp?via=mcp-registrystreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢validate_emails(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 verdict (deliverable_likely/risky/undeliverable/invalid), score 0-100 and reason codes per address. Does not verify that the mailbox itself exists.

Input Schema

{
  "type": "object",
  "properties": {
    "emails": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "maxItems": 10,
      "description": "Email addresses, also \"Name <email>\" or mailto: links. Up to 10."
    }
  },
  "required": [
    "emails"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools