verify_email_deliverability — email verify mcp MCP Tool
verify_email_deliverability
(verify email deliverability) is one of 2 tools on the
email verify mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_email_deliverability from your client
- Claude Code email verify mcp verify_email_deliverability run in your project directory
- Claude Desktop email verify mcp verify_email_deliverability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor email verify mcp verify_email_deliverability ~/.cursor/mcp.json
- VS Code email verify mcp verify_email_deliverability .vscode/mcp.json
- Zed email verify mcp verify_email_deliverability ~/.config/zed/settings.json
- Windsurf email verify mcp verify_email_deliverability ~/.codeium/windsurf/mcp_config.json
- Cline email verify mcp verify_email_deliverability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI email verify mcp verify_email_deliverability ~/.gemini/settings.json
- Grok email verify mcp verify_email_deliverability .mcp.json (in your project root)
- ChatGPT email verify mcp verify_email_deliverability Settings → Connectors → Advanced → Developer mode
- Claude.ai email verify mcp verify_email_deliverability Settings → Connectors → Add custom connector
- LangChain email verify mcp verify_email_deliverability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-verify-mcp https://email-verify-72343955726.us-central1.run.app/mcp/email-verifyOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 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.