Bulk Email Verifier — MillionVerifier BYOK & Dataset Input

io.github.myworkingmemoryPublished by GitHub account myworkingmemoryv2026.10.29Updated Oct 29, 2026

Bulk email verification for lists and Apify datasets; MillionVerifier BYOK, unbilled duplicates.

The publisher's own server: INPUT · buscador

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant bulk-verify email lists and Apify datasets through MillionVerifier with a bring-your-own key.

What you can do
  • Verify email addresses in bulk from a supplied list or an Apify dataset.
  • Run checks through MillionVerifier using the user's own API key (BYOK).
  • Skip duplicate addresses so they are not billed.
  • The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when you have a large list of email addresses or an Apify dataset and want an assistant to check deliverability in bulk before outreach or list cleanup.
Requirements
A remote MCP endpoint at mcp.apify.com with OAuth authentication; no local package or environment variables are declared. A MillionVerifier account and API key are needed for the bring-your-own-key verification.
Before you install
Verification is billed through your own MillionVerifier account, so bulk runs can cost money; duplicates are reported as unbilled. Email addresses you submit are sent to Apify and MillionVerifier as third parties. OAuth grants access to the Apify-hosted server.

Installation

In SourceWeft

  1. Open Bulk Email Verifier — MillionVerifier BYOK & Dataset Input 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.myworkingmemory%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-millionverifier-byok": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=myworkingmemory/email-verifier-bulk"
    }
  }
}

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. v2026.10.29LatestOct 29, 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 Input integrations