Kavik.email Email Verification

email.kavikPublished by kavik.emailOfficial publisherv1.0.1Updated Nov 22, 2026

Verify email addresses with provider-specific checks: single, lists, bulk jobs and domain audits.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Kavik.email remote MCP server that lets an assistant verify email addresses individually, in lists, in bulk jobs, and across whole domains.

What you can do
  • Verify single email addresses with provider-specific checks
  • Validate lists of addresses and run bulk verification jobs
  • Audit a domain's email setup and deliverability
When to use it
Useful when cleaning contact or signup lists, checking whether an address is deliverable before sending, or auditing a domain's email configuration.
Requirements
Remote streamable HTTP endpoint at mcp.kavik.email; no local install. OAuth clients can connect without extra setup; scripts send an Authorization header with a Bearer API key from the Kavik.email dashboard. Live checks require a paid plan or credit pack.
Before you install
Verification consumes plan credits or a credit pack, so usage can cost money. The Authorization header carries an API key that should be kept secret. Addresses submitted for verification are sent to a third-party service.

Installation

In SourceWeft

  1. Open Kavik.email 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/email.kavik%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": {
    "kavik-email-email-verification": {
      "type": "http",
      "url": "https://mcp.kavik.email/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.1LatestNov 22, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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