Mailvett: Email Validation API for AI Agents

io.github.CyberMax-toolsPublished by GitHub account CyberMax-toolsv1.0.0Updated 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, typo fixes and an overall pass

What you can do
Validate email addresses and return a verdict on whether they look usable, with MX record and provider information for the domain, flags for disposable, role-based and free-mail addresses, and suggested corrections for likely typos.
When to use it
Useful when an assistant needs to check email addresses before sign-up, outreach or list cleanup, and you want quick quality signals such as disposable or mistyped addresses without building your own validation logic.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared, and no authentication is declared. Network access to the hosted endpoint is required.
Before you install
Email addresses submitted for validation are sent to a third-party hosted service, so avoid sending sensitive or personal addresses you are not permitted to share. No authentication is declared, so anyone with the endpoint can call it.

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/io.github.CyberMax-tools%2Femail-validate/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.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 26, 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