What is Model Context Protocol (MCP)?

Created By
Abhi5h3ka year ago
A lightweight Model Context Protocol (MCP) server that enables your LLM to validate email addresses. This tool checks email format, domain validity, and deliverability using the AbstractAPI Email Validation API. Perfect for integrating email validation into AI applications like Claude Desktop.
Overview

What is MCP Email Verify?

MCP Email Verify is a lightweight Model Context Protocol (MCP) server designed to validate email addresses. It checks the format, domain validity, and deliverability of emails using the AbstractAPI Email Validation API, making it ideal for integrating email validation into AI applications like Claude Desktop.

How to use MCP Email Verify?

To use MCP Email Verify, clone the repository, set up the environment, and run the server. You can then register the server with Claude Desktop to start verifying email addresses.

Key features of MCP Email Verify?

  • Real-time email verification
  • Seamless integration with MCP-compatible LLMs
  • Easy setup using Python and the MCP SDK

Use cases of MCP Email Verify?

  1. Validating user email addresses in AI applications
  2. Ensuring deliverability of emails before sending
  3. Integrating email validation into chatbots and virtual assistants

FAQ from MCP Email Verify?

  • Can MCP Email Verify validate all email formats?

Yes, it checks for proper format, domain validity, and deliverability.

  • Is there a cost to use MCP Email Verify?

The tool is free to use, but you need an AbstractAPI key for validation.

  • What programming language is MCP Email Verify built with?

MCP Email Verify is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Abhi5h3k
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago