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