Email Validator Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Oct 25, 2026

Validate email addresses by format, MX record, and disposable domain. No key required.

VerifiedSTDIODesktop onlyCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that validates email addresses by format, MX record and disposable-domain checks, with no API key required.

What you can do
Check whether an email address is syntactically valid and correctly formatted. Verify that the address's domain has a usable MX record. Flag addresses on known disposable or throwaway domains. Combine these checks to judge whether an address is worth keeping or contacting.
When to use it
Useful when an assistant needs to screen email addresses before storing, sending to, or signing up with them, such as cleaning a contact list or checking user input.
Requirements
Runs as a local process via the npm package email-validator-mcp over stdio. No API key, environment variables or headers are declared. MX lookups need network access to DNS.
Before you install
MX checks send the address's domain to DNS resolvers, so domain names leave the machine. Results are heuristic: a valid format and MX record do not prove a mailbox exists or is deliverable.

Installation

In SourceWeft

  1. Open Email Validator Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestOct 17, 2026
  2. v1.0.1Sep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.