EmailVerify by Techforce Global

global.techforce.cloudPublished by cloud.techforce.globalOfficial publisherv1.0.0Updated Oct 29, 2026

Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that verifies email addresses for deliverability, returning a status, confidence score and reasons for each address.

What you can do
  • Verify a single address with syntax, domain/MX, disposable, role-account, live SMTP mailbox, catch-all, SPF/DMARC and typo checks, returning valid/invalid/risky/unknown status, a 0-100 confidence score, reasons and a did_you_mean suggestion.
  • Verify up to 50 addresses in one batch call, with duplicates checked once and a count per status plus full per-address results.
When to use it
Useful when cleaning a lead or contact list before an outreach campaign, or when an assistant needs to check whether a single address is likely to bounce or is a disposable, role or mistyped address.
Requirements
A remote streamable HTTP endpoint at cloud.techforce.global; no packages, environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
Addresses submitted are sent to a third-party verification service, which performs live SMTP checks against the recipient's mail server. Results are not guaranteed: unknown status is common for Gmail/Outlook rate limits, and risky covers catch-all, disposable and role accounts. Batch calls are limited to 50 addresses.

Installation

In SourceWeft

  1. Open EmailVerify by Techforce Global 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/global.techforce.cloud%2Femailverify/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": {
    "emailverify-by-techforce-global": {
      "type": "http",
      "url": "https://cloud.techforce.global/emailverify/mcp"
    }
  }
}

Tools

2

verify_email

Verify email address

Check if a single email address is real and deliverable. Runs syntax, domain/MX, disposable, role-account, live SMTP mailbox, catch-all, SPF/DMARC and typo checks, and returns status (valid / invalid / risky / unknown), a 0-100 confidence score, reasons and a did_you_mean suggestion for likely typos. Takes 1-20 seconds.

Parametersemailrequired

verify_email_batch

Verify a list of emails

Verify up to 50 email addresses in one call (for example a lead list before an outreach campaign). Returns a count per status (valid / invalid / risky / unknown) and the full result for each address. Duplicates are checked once. For larger lists, split into several calls.

Parametersemailsrequired

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

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

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