dns_record — nslookup MCP Tool
dns_record
(dns record) is one of 23 tools on the
nslookup
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dns_record from your client
- Claude Code nslookup dns_record run in your project directory
- Claude Desktop nslookup dns_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nslookup dns_record ~/.cursor/mcp.json
- VS Code nslookup dns_record .vscode/mcp.json
- Zed nslookup dns_record ~/.config/zed/settings.json
- Windsurf nslookup dns_record ~/.codeium/windsurf/mcp_config.json
- Cline nslookup dns_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nslookup dns_record ~/.gemini/settings.json
- Grok nslookup dns_record .mcp.json (in your project root)
- ChatGPT nslookup dns_record Settings → Connectors → Advanced → Developer mode
- Claude.ai nslookup dns_record Settings → Connectors → Add custom connector
- LangChain nslookup dns_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nslookup https://mcp.nslookup.io/mcpOther tools on this server
- dns_lookup
- dns_propagation
- webservers
- ssl_certificate
- bimi_vmc
- security_scan
- uptime_check
- uptime_check_multi
- dns_health
- geo_checker
- rdap_lookup
- hosting_report
- domain_scanner
- dns_change_review
- bimi_check
- status_page
- my_overview
- my_monitors
- my_incidents
- my_uptime_history
- my_dns_changes
- my_certificates
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.