Email Checker MCP Server
For your cold outbound email, this tool will help you validate email addresses.
Features
- Email address validation
- Simple JSON response format
- No API key required
Prerequisites
- Python 3.x
Installation
- Clone the repository:
git clone https://github.com/ravinahp/email-checker-mcp.git
cd email-checker-mcp
- Install dependencies using uv:
uv sync
Note: We use uv instead of pip since the project uses pyproject.toml for dependency management.
Configure as MCP Server
To add this tool as an MCP server, you'll need to modify your Claude desktop configuration file.
The configuration file location depends on your operating system:
- MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
Add the following configuration to your JSON file:
{
"email-checker-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/YOUR_USERNAME/Code/email-checker-mcp",
"run",
"email-checker-mcp"
]
}
}
⚠️ IMPORTANT:
- Replace
YOUR_USERNAMEwith your actual system username - Make sure the directory path matches your local installation
Usage
The service provides a FastMCP tool for validating email addresses:
@mcp.tool()
async def validate_email(email: str) -> bool:
"""Validate if an email address exists."""
Example Use:
Prompt: Does this email exist?
Parameters:
email: String containing the email address to validate
Example Response:
{
"exist": true
}
API Usage Limits
The service uses 2IP's Email API which provides:
- No API key required
Error Handling
The service includes error handling for:
- Invalid email format
- API request failures
- Network timeouts
- Rate limiting
Metadata
Release files for iflow-mcp_email-checker-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_email_checker_mcp-0.1.0.tar.gz | 14.1 kB | Without provenance | Details for iflow_mcp_email_checker_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_email_checker_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_email_checker_mcp-0.1.0-py3-none-any.whl |
Total release size: 18.3 kB
Release files / iflow_mcp_email_checker_mcp-0.1.0.tar.gz
| Download URL | iflow_mcp_email_checker_mcp-0.1.0.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46db85aaaf5ec0d6b5a2f709450aa35cf7e3c6e01a4c5dd09e85481576216cdc
|
|
BLAKE2b-256 checksum How to use checksums |
596a4e356aadd83cfd0ef5ad23cac7db5229ecc0f6d9b40648f6cb30842c292f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Release files / iflow_mcp_email_checker_mcp-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_email_checker_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1442678b8649a112326b55014857114b2fdea1ff25d192c42b0e7fd1b8f1f549
|
|
BLAKE2b-256 checksum How to use checksums |
689825e2429635df1b22ff15f9063a05fe76f73fb79e3c6699bbd03dc80dc216
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Security for iflow-mcp_email-checker-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.