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