ipatlas MCP

A hosted remote MCP server that provides IP geolocation capabilities to AI agents. It allows agents to determine the country, region, city, time zone, and ASN for any IPv4 or IPv6 address. The server offers three main tools: lookup_ip for single address queries, my_location to identify the caller's public IP and location, and lookup_batch for processing up to 100 IPs simultaneously. It operates via standard MCP Streamable HTTP without requiring local installation or database maintenance.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-19Operated by ipatlas

MCP endpoint (Streamable HTTP)

https://api.ipatlas.dev/mcp

Vendor documentation

What you can do with it

Check the public IP and location of the machine calling the API
Look up geolocation details for a single IPv4 or IPv6 address
Batch lookup up to 100 IPs to investigate access logs or sign-ins

Tools advertised by the last live check:

lookup_ip
my_location
lookup_batch

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http ipatlas-mcp https://api.ipatlas.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add ipatlas-mcp --url https://api.ipatlas.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable ipatlas-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "ipatlas-mcp": {
      "url": "https://api.ipatlas.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "ipatlas-mcp": {
      "type": "streamableHttp",
      "url": "https://api.ipatlas.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start ipatlas-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "ipatlas-mcp": {
      "type": "http",
      "url": "https://api.ipatlas.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http ipatlas-mcp https://api.ipatlas.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "ipatlas-mcp": {
      "url": "https://api.ipatlas.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "ipatlas-mcp": {
      "serverUrl": "https://api.ipatlas.dev/mcp"
    }
  }
}

Ground your agent in cited data

ipatlas MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Connect Koskamo Browse datasets

See all 1,282

Do you run ipatlas MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing