Kawaa email verification

com.kawaaPublished by kawaa.comOfficial publisherv1.0.1Updated Oct 24, 2026

Check whether an email address can receive mail, one address or a list, without sending to it.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant check whether an email address can receive mail, for a single address or a list, without sending to it.

What you can do
  • Check a single email address for deliverability without sending mail to it.
  • Check a list of email addresses in one request.
  • Return a result per address indicating whether it can receive mail.
When to use it
Useful when cleaning contact or signup lists, validating addresses before a campaign, or checking a user-supplied address before relying on it. It is a narrow, single-purpose service rather than a general email tool.
Requirements
A remote MCP client connecting to the provider's hosted endpoint over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no local package is needed.
Before you install
Addresses submitted for verification are sent to a third party, so consider whether that is acceptable for personal or customer data. The manifest declares no authentication, so check the provider's terms, rate limits and data handling before relying on it.

Installation

In SourceWeft

  1. Open Kawaa email verification 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/com.kawaa%2Femail-verification/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": {
    "kawaa-email-verification": {
      "type": "http",
      "url": "https://api.kawaa.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.1LatestOct 15, 2026
  2. v1.0.0Sep 20, 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 listedRequired15 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.