my_dns_changes — nslookup MCP Tool
my_dns_changes
(my dns changes) 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 my_dns_changes from your client
- Claude Code nslookup my_dns_changes run in your project directory
- Claude Desktop nslookup my_dns_changes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nslookup my_dns_changes ~/.cursor/mcp.json
- VS Code nslookup my_dns_changes .vscode/mcp.json
- Zed nslookup my_dns_changes ~/.config/zed/settings.json
- Windsurf nslookup my_dns_changes ~/.codeium/windsurf/mcp_config.json
- Cline nslookup my_dns_changes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nslookup my_dns_changes ~/.gemini/settings.json
- Grok nslookup my_dns_changes .mcp.json (in your project root)
- ChatGPT nslookup my_dns_changes Settings → Connectors → Advanced → Developer mode
- Claude.ai nslookup my_dns_changes Settings → Connectors → Add custom connector
- LangChain nslookup my_dns_changes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nslookup https://mcp.nslookup.io/mcpOther 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.