monitored-domains — dns doctor MCP Resource

monitored-domains is one of 1 resource on the dns doctor MCP server. Connect the server and your client can attach it as context.

by client

How to attach monitored-domains from your client

• Claude Code dns doctor Resource/monitored-domains run in your project directory
• Claude Desktop dns doctor Resource/monitored-domains ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor dns doctor Resource/monitored-domains ~/.cursor/mcp.json
• VS Code dns doctor Resource/monitored-domains .vscode/mcp.json
• Zed dns doctor Resource/monitored-domains ~/.config/zed/settings.json
• Windsurf dns doctor Resource/monitored-domains ~/.codeium/windsurf/mcp_config.json
• Cline dns doctor Resource/monitored-domains ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI dns doctor Resource/monitored-domains ~/.gemini/settings.json
• Grok dns doctor Resource/monitored-domains .mcp.json (in your project root)
• ChatGPT dns doctor Resource/monitored-domains Settings → Connectors → Advanced → Developer mode
• Claude.ai dns doctor Resource/monitored-domains Settings → Connectors → Add custom connector
• LangChain dns doctor Resource/monitored-domains pip install langchain-mcp-adapters

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.