Bulk Email Verifier & Validator

io.github.monietoolsPublished by GitHub account monietoolsv1.0.0Updated Oct 27, 2026

Check emails for valid syntax, MX records, disposable and role addresses and typos. No SMTP check.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant bulk-check email addresses for syntax, MX records, disposable and role addresses, and typos.

What you can do
  • Validate email addresses in bulk: check syntax and domain MX records.
  • Flag disposable domains, role-based addresses and likely typos.
  • Note that no SMTP mailbox check is performed, so results are format and domain level only.
When to use it
Useful when cleaning a contact or signup list before outreach or import, or when an assistant needs to screen addresses for obvious problems without sending mail.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. An Apify API token sent as an Authorization Bearer header, or OAuth sign-in if the client supports it. Network access to Apify.
Before you install
Requires an Apify account and API token, which is a credential to keep private. Apify usage may be subject to plan limits or charges. Addresses you submit are sent to a third-party service. No SMTP check, so a passing result does not prove a mailbox exists.

Installation

In SourceWeft

  1. Open Bulk Email Verifier & Validator in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.monietools%2Femail-verifier-bulk/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bulk-email-verifier-validator": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=poised_beardlichen/email-verifier-bulk"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 19, 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 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.