IPinfo

IPinfo MCP Server

The official IPinfo MCP Server lets AI assistants such as Claude answer questions about IP addresses. Ask where an IP is located, which company or network it belongs to, or whether it's a VPN, proxy, Tor exit node, or residential proxy, and the assistant looks it up with IPinfo data.

It implements the Model Context Protocol (MCP), the open standard AI assistants use to connect to external tools, so it works with any MCP-compatible client. It supports the IPinfo Lite, Core, Plus, and Residential Proxy plans.

For the full guide, see the official documentation.

[OpenSSF Scorecard] [OpenSSF Best Practices]

Installation

You need an IPinfo account. Sign up for free at ipinfo.io/signup.

Hosted server

Point your MCP client at https://mcp.ipinfo.io/ (Streamable HTTP). The first time it connects, it asks you to sign in with your IPinfo account through OAuth.

Local server (PyPI)

The server is published on PyPI as ipinfo-mcp-server and runs over stdio, authenticating with your API token. With uv installed, add it to your MCP client configuration:

{  "mcpServers": {    "ipinfo": {      "command": "uvx",      "args": ["ipinfo-mcp-server"],      "env": {        "IPINFO_TOKEN": "<your-ipinfo-token>"      }    }  }}

Claude Desktop extension

Download mcp.mcpb from the latest GitHub release and open it with Claude Desktop. You'll be asked for your API token during installation.

MCP Registry

The server is listed in the MCP Registry as io.github.ipinfo/mcp.

The server is also listed on LightNow.

Tools

Tools that lack access for the token's plan return an ACCESS_DENIED error.

Common parameters

All tools except ipinfo_quota take a list of IPs and are paginated:

ipinfo_lookup, ipinfo_geolocate, and ipinfo_asn also take:

Common output

IP-based tools return:

If the whole request fails (for example a missing or invalid token), the tool returns an error object instead, with code (ACCESS_DENIED, RATE_LIMITED, INVALID_TOKEN, NO_TOKEN, API_ERROR, or UNKNOWN), message, and suggestion.

ipinfo_lookup

Returns the raw IPinfo API response for each IP.

• detailed: false (Lite): ip, asn, as_name, as_domain, country, country_code, continent, continent_code.
• detailed: true (full lookup): ip, hostname, geo (city, region, country, continent, coordinates, timezone, postal code), as (ASN, name, domain, type), anonymous (proxy, relay, Tor, VPN), mobile, and the is_anonymous, is_anycast, is_hosting, is_mobile, is_satellite flags. Some fields are only available on Plus.

ipinfo_geolocate

Returns, per IP: ip, country, country_code, continent, continent_code. With detailed: true, also city, region, region_code, latitude, longitude, timezone, postal_code.

ipinfo_asn

Returns, per IP: ip, asn, name, domain. With detailed: true, also type (isp, hosting, business, education) and last_changed.

ipinfo_check_privacy

Returns, per IP: ip, is_anonymous, anonymous (is_proxy, is_relay, is_tor, is_vpn), is_anycast, is_hosting, is_mobile, is_satellite.

ipinfo_check_residential_proxy

Returns, per IP: ip and is_residential_proxy. For residential proxies, also service (proxy service name), last_seen (date), and percent_days_seen.

ipinfo_quota

Takes no parameters. Returns token (omitted when connected with OAuth), requests (day, month, limit, remaining), and per-feature quotas under features.

Configuration

The server is configured through environment variables:

With the http transport, each request authenticates with its own Authorization: Bearer <token> header.

Setting IPINFO_OAUTH_ISSUER turns on OAuth for the http transport. The server then advertises the issuer at /.well-known/oauth-protected-resource, answers requests without a valid credential with 401 Unauthorized, and verifies access tokens against the issuer's signing keys. A verified access token is sent to the IPinfo API in place of an API token. API tokens keep working as before.

Feedback

• Bugs and feature requests: open an issue on GitHub Issues.
• Security vulnerabilities: don't open a public issue; follow the security policy.
• Questions about your IPinfo account or plan: contact [email protected].

Contributing

Contributions are welcome. See CONTRIBUTING.md for the workflow and the requirements a change has to meet.

Development

Prerequisites

• Python 3.14+
• uv

Setup

uv sync --devcp .env.example .env# Add your IPinfo token to .env

Running the server

The server supports two transports: stdio (default) and HTTP.

# stdio (default, used by MCP clients)uv run ipinfo-mcp-server
# HTTPIPINFO_TRANSPORT=http HOST=0.0.0.0 PORT=8000 uv run ipinfo-mcp-server

Tests

# All testsuv run pytest
# Integration tests (requires IPINFO_TOKEN)uv run pytest tests/integration/

Integration tests hit the real IPinfo API and validate response structure only (no exact value assertions). They require IPINFO_TOKEN to be set and are skipped otherwise.

Type checking

uv run pyright

Linting

uv run ruff check .uv run ruff format .