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