Bulk Email Verifier & MX Check

io.github.winters-works-coPublished by GitHub account winters-works-cov1.0.0Updated Oct 24, 2026

Email list check: syntax, domain, MX records, disposable/role addresses (DNS level). Winters Works.

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

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant check email lists at the DNS level for syntax, domain, MX records, and disposable or role addresses.

What you can do
Check email addresses for syntax and domain validity at the DNS level, including MX records and disposable or role addresses.
When to use it
Useful when you need to clean or screen an email list before outreach and want an assistant to flag invalid, disposable or role-based addresses without leaving the conversation.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP. Authentication is required: either an Apify API token sent as a Bearer value in the Authorization header, or OAuth sign-in with Apify.
Before you install
You must supply an Apify API token or sign in with Apify, so the server is tied to your Apify account and any usage limits or costs that apply. Email addresses you submit are sent to a third-party service for checking.

Installation

In SourceWeft

  1. Open Bulk Email Verifier & MX Check 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.winters-works-co%2Fbulk-email-verifier/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-mx-check": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=wintersworks/bulk-email-verifier-dns"
    }
  }
}

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 13, 2026

Score

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

  • 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