The official IPGeolocation.io MCP server provides 17 tools for accurate IP geolocation, company information, ASN and network data, IP security (VPN, proxy, Tor, bot, hosting and spam detection), abuse contacts, time zones, astronomy, currency data and user-agent parsing.
This repository packages the 2.0.3 release for Linux amd64 and arm64. The manual workflow tests and builds the release source from commit fce963047a120db33b5fdcb37fd3e50e1eea1f42 with Node.js 24.22.1 on a pinned Alpine 3.24 base. It removes BusyBox and package installers from the runtime while retaining UID 65532, stdio startup and HTTPS support. Native amd64 and arm64 checks run before publication. It scans both architectures, publishes an SBOM and build provenance, and signs the image digest. It refuses to overwrite the 2.0.3 container tag.
Set IPGEOLOCATION_API_KEY in the private environment that launches your MCP client:
docker run --rm -i --env IPGEOLOCATION_API_KEY ghcr.io/ipgeolocation/ipgeolocation-io-mcp:2.0.3ToolHive can run the same image:
thv run --env NODE_USE_ENV_PROXY=1 ghcr.io/ipgeolocation/ipgeolocation-io-mcp:2.0.3The proxy setting lets Node.js use ToolHive’s isolated network.
Use ToolHive’s secret provider to supply IPGEOLOCATION_API_KEY for authenticated lookups. get_my_ip works without a key or credits. Cached-result retrieval reads the running server’s memory and uses the original lookup’s key. Available data depends on your IPGeolocation.io plan.
The container runs as an unprivileged user over stdio. The build removes the shell, npm, Yarn, Corepack and apk. It needs outbound HTTPS to api.ipgeolocation.io for API lookups and requires no host-directory mounts. It contains no API key. See the server documentation for tool inputs and client setup.
Security policy · Privacy policy · Support
License: MIT. Source and releases: IPGeolocation/ipgeolocation-io-mcp.