
IPinfo
io.github.ipinfoPublished by GitHub account ipinfov0.2.3Updated Oct 29, 2026
Official IPinfo MCP Server - IP intelligence tools for AI assistants
Overview
Official IPinfo server that lets an assistant look up IP addresses for geolocation, network ownership, and VPN, proxy, Tor, or residential proxy detection.
- What you can do
- Look up full IP data, geolocation, and network ownership (ASN) for lists of public IPv4/IPv6 addresses, with a detailed mode for richer fields
- Check privacy signals per IP: VPN, proxy, relay, Tor, hosting, anycast, mobile, and satellite flags
- Detect residential proxies, including the proxy service name and how recently it was seen
- Check API usage and remaining quota for the token
- Page through large IP lists and see per-IP errors and validation errors for invalid addresses
- When to use it
- Useful when an assistant needs to interpret IP addresses in logs, sign-ups, or support tickets: where a visitor is, which network or company they come from, or whether traffic looks like a VPN, Tor, or residential proxy. It fits fraud, abuse, and access-analysis questions rather than general web search.
- Requirements
- An IPinfo account and API token (IPINFO_TOKEN) for the local PyPI package, which runs over stdio via uvx; the hosted endpoint at mcp.ipinfo.io uses OAuth sign-in instead. Some tools need a paid plan or Residential Proxy access. Python 3.14+ and uv only if running from source.
Installation
In SourceWeft
- Open IPinfo in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ipinfo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ipinfo": {
"type": "http",
"url": "https://mcp.ipinfo.io/"
}
}
}README
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:
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 theis_anonymous,is_anycast,is_hosting,is_mobile,is_satelliteflags. 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
Running the server
The server supports two transports: stdio (default) and HTTP.
Tests
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
Linting
Source: README.md at commit f4b89e3
Tools
0Version history
6- v0.2.3LatestOct 29, 2026
- v0.2.1Oct 22, 2026
- v0.2.0Oct 21, 2026
- v0.1.14Oct 1, 2026
- v0.1.13Sep 24, 2026
- v0.1.12Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts