Checkmails — Email Verification

eu.checkmailsPublished by checkmails.euOfficial publisherv1.0.0Updated Oct 24, 2026

Verify email deliverability by SMTP. Catch-all/disposable/role detection. EU-hosted, GDPR-ready.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant verify email addresses for deliverability via SMTP, with catch-all, disposable and role detection.

What you can do
Verify whether an email address is deliverable using SMTP checks, so an assistant can flag bad or risky addresses before you use them. Detect catch-all domains, disposable addresses and role-based mailboxes to judge how trustworthy a contact is. Results come from an EU-hosted, GDPR-oriented service.
When to use it
Useful when cleaning contact or signup lists, checking addresses before sending campaigns, or validating an email an assistant is about to use in a workflow.
Requirements
A remote endpoint at checkmails.eu over streamable HTTP. Requires a bearer token in the Authorization header (a checkmails API key) from a paid checkmails plan. No local runtime or environment variables.
Before you install
The API key is sent as a bearer token in the Authorization header, so keep it private. The service is paid, so checks may consume plan quota or cost money. Email addresses you submit are sent to a third-party service for verification.

Installation

In SourceWeft

  1. Open Checkmails — Email Verification in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/eu.checkmails%2Fcheckmails/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": {
    "checkmails-email-verification": {
      "type": "http",
      "url": "https://checkmails.eu/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.