Email Validator

io.github.ryuamarinesPublished by GitHub account ryuamarinesv1.0.92767Updated Oct 29, 2026

Validates email syntax and MX records. x402 payment required (Base mainnet USDC).

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server with one tool that checks an email address's syntax and MX records, charging per call via x402 in USDC on Base mainnet.

What you can do
Validate an email address: check its syntax and look up the domain's MX records to see whether it can receive mail.
When to use it
Useful when an assistant needs a quick syntax and MX check on an address, for example while cleaning a contact list or screening form input, and you are willing to pay per call.
Requirements
A remote endpoint reached over streamable HTTP; no package, account, API key or environment variable is declared. Each call requires an x402 payment in USDC on Base mainnet, so a compatible paying client and funded wallet are needed.
Before you install
The tool is paid: every call requires an x402 payment in USDC on Base mainnet, which spends real funds. No authentication is declared, so anyone with the endpoint can call it. Addresses submitted are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Email Validator 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.ryuamarines%2Femail-validator/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-validator": {
      "type": "http",
      "url": "https://ai-factory-mcp.ryuamarines.workers.dev/email-validator/mcp"
    }
  }
}

README

This repository has no README.

Tools

1

email_validator

Validates email syntax and MX records. x402 payment required (Base mainnet USDC).

ParametersemailsrequiredcheckMxpayment

Version history

2
  1. v1.0.92767LatestOct 29, 2026
  2. v1.0.92766Sep 16, 2026

Score

75% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.