my_monitors — nslookup MCP Tool

my_monitors (my monitors) 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_monitors from your client

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

Fastest route

claude mcp add --transport http nslookup https://mcp.nslookup.io/mcp

Other tools on this server

dns_lookup
dns_record
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_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.

nslookup MCP server