resolver_status — is it DNS? MCP Tool
resolver_status
(resolver status) is one of 8 tools on the
is it DNS?
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolver_status from your client
- Claude Code is it DNS? resolver_status run in your project directory
- Claude Desktop is it DNS? resolver_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor is it DNS? resolver_status ~/.cursor/mcp.json
- VS Code is it DNS? resolver_status .vscode/mcp.json
- Zed is it DNS? resolver_status ~/.config/zed/settings.json
- Windsurf is it DNS? resolver_status ~/.codeium/windsurf/mcp_config.json
- Cline is it DNS? resolver_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI is it DNS? resolver_status ~/.gemini/settings.json
- Grok is it DNS? resolver_status .mcp.json (in your project root)
- ChatGPT is it DNS? resolver_status Settings → Connectors → Advanced → Developer mode
- Claude.ai is it DNS? resolver_status Settings → Connectors → Add custom connector
- LangChain is it DNS? resolver_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http isitdns https://isitdns.net/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.