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