scan_domain — dns doctor MCP Tool
scan_domain
(scan domain) is one of 20 tools on the
dns doctor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_domain from your client
- Claude Code dns doctor scan_domain run in your project directory
- Claude Desktop dns doctor scan_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dns doctor scan_domain ~/.cursor/mcp.json
- VS Code dns doctor scan_domain .vscode/mcp.json
- Zed dns doctor scan_domain ~/.config/zed/settings.json
- Windsurf dns doctor scan_domain ~/.codeium/windsurf/mcp_config.json
- Cline dns doctor scan_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dns doctor scan_domain ~/.gemini/settings.json
- Grok dns doctor scan_domain .mcp.json (in your project root)
- ChatGPT dns doctor scan_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai dns doctor scan_domain Settings → Connectors → Add custom connector
- LangChain dns doctor scan_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dns-doctor https://dnsdoctor.dev/mcpOther tools on this server
- get_report
- build_dmarc_upgrade
- start_monitoring_signup
- count_spf_lookups
- validate_dmarc_record
- generate_dmarc_record
- check_dkim_selector
- parse_dmarc_report
- check_record
- check_reverse_dns
- audit_spf_includes
- build_parked_domain_records
- check_propagation
- lookup_registration
- get_alerts
- get_readiness
- add_monitored_domain
- check_domain_verification
- get_domain_records
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.