Mailvett: Email Validation API for AI Agents

dev.workers.cybermax-tools.cybermaxPublished by cybermax.cybermax-tools.workers.devv1.0.2Updated Oct 24, 2026

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

The publisher's own server: email-validation.org email validation

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant validate email addresses, checking MX records, provider, disposable/role/free flags, typos and an overall verdict.

What you can do
Validate email addresses and return an overall verdict on whether they look deliverable or usable. Check domain mail setup through MX records and identify the email provider. Flag disposable, role-based and free-mailbox addresses. Suggest corrections for likely typos in the address.
When to use it
Useful when an assistant needs to check email addresses before sign-up, outreach or list cleaning, or to spot disposable, role or mistyped addresses in user-supplied data.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An optional paid-plan API key is supplied in the x-api-key header; leaving it out uses the free daily tier.
Before you install
The x-api-key header carries a paid-plan credential, so keep it out of logs and shared transcripts. Validation results are heuristic and should not be treated as proof an address is deliverable. Addresses submitted are sent to a third-party service.

Installation

In SourceWeft

  1. Open Mailvett: Email Validation API for AI Agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.cybermax-tools.cybermax%2Fmailvett/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mailvett-email-validation-api-for-ai-age": {
      "type": "http",
      "url": "https://mailvett.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.2LatestOct 10, 2026
  2. v1.0.1Oct 10, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Email-Validation integrations