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