PingValid Email Validation

com.pingvalidPublished by pingvalid.comOfficial publisherv0.4.3Updated Oct 28, 2026

Email validation for AI assistants: verdict, risk score, evidence. Free: 100 checks a month.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote PingValid MCP server that lets an assistant validate email addresses and return a verdict, risk score and supporting evidence.

What you can do
  • Validate email addresses, returning a verdict, a risk score and the evidence behind it.
  • Check addresses during signup, list cleaning or outreach preparation.
  • Free tier covers 100 checks per month.
When to use it
Useful when an assistant needs to judge whether an email address is deliverable or risky, for example before adding contacts to a list, qualifying leads, or checking addresses collected in a workflow.
Requirements
Remote streamable HTTP endpoint at pingvalid.com; no local package. Authentication is required: OAuth sign-in by default, or an Authorization header carrying a PingValid API key (pv_live_…) created in the PingValid dashboard. A PingValid account is needed; free plan allows 100 checks a month.
Before you install
The Authorization header carries a live API key secret; keep it out of logs and shared transcripts. Email addresses you submit are sent to PingValid for checking, so consider whether that data is appropriate to share with a third party. Usage beyond the free monthly quota may require a paid plan.

Installation

In SourceWeft

  1. Open PingValid Email Validation 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/com.pingvalid%2Fmcp-server/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": {
    "pingvalid-email-validation": {
      "type": "http",
      "url": "https://pingvalid.com/mcp"
    }
  }
}

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

3
  1. v0.4.3LatestOct 18, 2026
  2. v0.4.2Oct 2, 2026
  3. v0.4.1Sep 16, 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.