Email Check

io.github.DawaxwxPublished by GitHub account Dawaxwxv0.1.0Updated Oct 24, 2026

Fast email validation at the edge: syntax, MX records, disposable-domain detection.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant validate email addresses, checking syntax, MX records and disposable domains.

What you can do
It exposes a single tool, run, which performs fast email validation at the edge. The check covers address syntax, MX record lookup for the domain, and detection of disposable email domains. It is a lightweight lookup service rather than a mailbox verification tool.
When to use it
Useful when an assistant needs to screen email addresses before sign-up, outreach or form submission, for example filtering out malformed or throwaway addresses. Less suited to confirming that a specific mailbox actually exists.
Requirements
Runs as a remote streamable HTTP endpoint; no local package, account, API key or environment variable is declared. Network access to the endpoint is required.
Before you install
Addresses submitted for validation are sent to a third-party remote service, so avoid sending sensitive or personal email data you would not share externally. The input does not state whether results are logged or retained.

Installation

In SourceWeft

  1. Open Email Check 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.Dawaxwx%2Femail-check/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": {
    "email-check": {
      "type": "http",
      "url": "https://email-check.david-cyr.workers.dev/mcp"
    }
  }
}

Tools

1

run

Fast email validation at the edge: syntax, MX records, disposable-domain detection.

Parametersinputrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Check integrations