MCP Ip2location IO

What ip2location/mcp-ip2location-io MCP server does

The ip2location/mcp-ip2location-io MCP server connects an MCP client to the IP2Location.io API for IP address intelligence. It accepts IPv4 and IPv6 addresses and returns a JSON result with location, network, autonomous system, mobile, language, currency, proxy, and other available attributes.

Its main tool, get_geolocation, handles one address or a group of addresses. Results can include country, region, district, city, postal code, coordinates, time zone, ASN, ISP, domain, connection speed, usage type, mobile network codes, currency, language, proxy details, threat information, fraud score, weather, elevation, population, and related fields. The exact response depends on the IP2Location.io subscription.

Typical uses include examining IPs found in application logs, adding geographic context to datasets, investigating network ownership, checking proxy-related signals, and supporting localization or traffic analysis workflows.

How it works

The MCP client sends an address string to get_geolocation. For several addresses, provide them in one request as a comma-separated string; the server is instructed to batch them rather than issue sequential tool calls. The README also documents space- or newline-separated input in natural-language requests. When bulk processing is available for the account, the server routes multiple addresses to the IP2Location.io Bulk API.

The response is a JSON string. A single lookup returns the data for that address, while a bulk lookup returns an object mapping each queried IP to its result. Invalid or failed single-address requests produce an error string. The server makes asynchronous HTTP requests through httpx.

Setup and configuration

The ip2location/mcp-ip2location-io MCP server can be used through the hosted IP2Location.io MCP endpoint or run locally. The documented local setup uses Python 3.13 or newer, uv, an MCP-compatible client, and an IP2Location.io API key. Claude Desktop is the client shown in the setup instructions.

For a local configuration, run the package with uvx and set the IP2LOCATION_API_KEY environment variable to the key from the IP2Location.io account. Do not commit that key to a public repository. The hosted configuration uses the IP2Location.io MCP endpoint and passes the key in an X-API-Key header through the client configuration.

IP2Location.io offers a free API plan with up to 50,000 IP Geolocation API queries per month and basic information. The underlying REST API also permits limited keyless access, but the documented MCP setup recommends configuring an API key. Higher plans expose more attributes and quotas, and bulk lookup requires an eligible paid plan.

Tools and capabilities

• get_geolocation: Looks up one IPv4 or IPv6 address or a batch of addresses.
• Geographic data: country, region, city, postal code, coordinates, and time zone.
• Network data: ASN, AS details, ISP, domain, speed, address type, and usage type.
• Proxy and security data: proxy status and type, provider, last-seen information, threat data, and fraud score when available.
• Additional plan-dependent data: mobile, currency, language, weather, elevation, population, and IAB category information.

The tool returns the API’s JSON result. Client instructions specify that the raw JSON object should be preserved rather than summarized or reformatted.

Limitations and notes

Returned fields are controlled by the IP2Location.io plan. Proxy, VPN, Tor, data-center, threat, fraud, and other extended attributes may require supported paid access. Bulk requests likewise depend on an eligible paid plan. An API key is required by the recommended configuration, even though the underlying API documents limited keyless access.

The ip2location/mcp-ip2location-io MCP server provides one documented MCP tool, so it is focused on IP lookup rather than general-purpose network administration. Address input should be batched into one tool call when multiple IPs are supplied.