my_uptime_history — nslookup MCP Tool
my_uptime_history
(my uptime history) 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_uptime_history from your client
- Claude Code nslookup my_uptime_history run in your project directory
- Claude Desktop nslookup my_uptime_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nslookup my_uptime_history ~/.cursor/mcp.json
- VS Code nslookup my_uptime_history .vscode/mcp.json
- Zed nslookup my_uptime_history ~/.config/zed/settings.json
- Windsurf nslookup my_uptime_history ~/.codeium/windsurf/mcp_config.json
- Cline nslookup my_uptime_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nslookup my_uptime_history ~/.gemini/settings.json
- Grok nslookup my_uptime_history .mcp.json (in your project root)
- ChatGPT nslookup my_uptime_history Settings → Connectors → Advanced → Developer mode
- Claude.ai nslookup my_uptime_history Settings → Connectors → Add custom connector
- LangChain nslookup my_uptime_history 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.