verify_email — Email List Validation Email Verification MCP Tool
verify_email
(verify email) is one of 9 tools on the
Email List Validation Email Verification
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_email from your client
- Claude Code Email List Validation Email Verification verify_email run in your project directory
- Claude Desktop Email List Validation Email Verification verify_email ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Email List Validation Email Verification verify_email ~/.cursor/mcp.json
- VS Code Email List Validation Email Verification verify_email .vscode/mcp.json
- Zed Email List Validation Email Verification verify_email ~/.config/zed/settings.json
- Windsurf Email List Validation Email Verification verify_email ~/.codeium/windsurf/mcp_config.json
- Cline Email List Validation Email Verification verify_email ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Email List Validation Email Verification verify_email ~/.gemini/settings.json
- Grok Email List Validation Email Verification verify_email .mcp.json (in your project root)
- ChatGPT Email List Validation Email Verification verify_email Settings → Connectors → Advanced → Developer mode
- Claude.ai Email List Validation Email Verification verify_email Settings → Connectors → Add custom connector
- LangChain Email List Validation Email Verification verify_email pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-verification https://app.emaillistvalidation.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.