# IPinfo (remote · mcp.ipinfo.io)

Official IPinfo MCP Server - IP intelligence tools for AI assistants

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.ipinfo.io`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ipinfo-mcp/mcp.md), [page](https://verifymcp.io/servers/ipinfo-mcp/mcp)
- pypi · `ipinfo-mcp-server`: 36/100, [markdown](https://verifymcp.io/servers/ipinfo-mcp/ipinfo-mcp-server.md), [page](https://verifymcp.io/servers/ipinfo-mcp/ipinfo-mcp-server)

## Channel facts

- Endpoint: `https://mcp.ipinfo.io/`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.12`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2149 tokens (~358/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the IPinfo MCP server?

IPinfo is a hosted endpoint at https://mcp.ipinfo.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ipinfo-mcp 'https://mcp.ipinfo.io/'
```

### Cursor

```json
{
  "mcpServers": {
    "ipinfo-mcp": {
      "url": "https://mcp.ipinfo.io/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ipinfo-mcp": {
      "type": "http",
      "url": "https://mcp.ipinfo.io/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ipinfo-mcp]
url = "https://mcp.ipinfo.io/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ipinfo-mcp": {
      "type": "remote",
      "url": "https://mcp.ipinfo.io/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ipinfo-mcp --url 'https://mcp.ipinfo.io/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ipinfo-mcp:
    url: "https://mcp.ipinfo.io/"
```

### Netclaw

```json
{
  "McpServers": {
    "ipinfo-mcp": {
      "Transport": "http",
      "Url": "https://mcp.ipinfo.io/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ipinfo-mcp -t streamable-http -u 'https://mcp.ipinfo.io/'
```

### Other

```json
{
  "mcpServers": {
    "ipinfo-mcp": {
      "type": "http",
      "url": "https://mcp.ipinfo.io/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 65)

First indexed and scored.

## MCP tools (6)

### `ipinfo_lookup` (~440 tokens)

Look up geolocation, network, and metadata for one or more IP addresses.

By default queries the IPinfo Lite endpoint, which returns country, continent, and ASN info.
Set detailed=True to query the full lookup endpoint, which adds city-level geolocation,
privacy flags (VPN, proxy, Tor, hosting, anycast), and richer AS data.

Results are paginated. Use page and page_size to control which slice is returned.

If the API reports an error for specific IPs, those IPs are listed in errors
with the reason and left out of results.

Results are cached in memory for the session, so repeat lookups of the same IP
are served from cache without consuming API quota. You do not need to maintain
your own cache or deduplicate IPs before calling this tool. The _meta field
reports api_calls_made and from_cache counts.

Input parameters:

- `detailed` (boolean): Which IPinfo endpoint to query. Leave false to use the Lite endpoint, which returns country, continent, and basic ASN. Set to true to use the full lookup endpoint, which also returns city-level geolo…
- `ips` (array, required): Public IP addresses to query, IPv4 or IPv6, e.g. ["8.8.8.8", "2001:4860:4860::8888"]. Private, loopback, reserved, multicast, and bogon addresses are rejected: they are reported under validation_erro…
- `page` (integer): Page of the result set to return, 1-based. Values below 1 are clamped to 1, and a page past the last one returns no results.
- `page_size` (integer): How many IPs to resolve and return per page. Clamped to a maximum of 1000, the API batch limit. Only the IPs on the requested page are fetched, so a smaller page size consumes less quota per call.

Output parameters:

- `result`

### `ipinfo_check_privacy` (~344 tokens)

Check whether IP addresses are using privacy or anonymity services.

Returns privacy flags for each IP: whether it is anonymous, using a VPN, proxy,
relay, or Tor, and whether it is an anycast, hosting, mobile, or satellite address.

Requires a paid API token. Results are paginated.

If the API reports an error for specific IPs, those IPs are listed in errors
with the reason and left out of results. Do not treat a missing result as
"no privacy services detected": check errors.

Results are cached in memory for the session, so repeat checks of the same IP
are served from cache without consuming API quota. You do not need to maintain
your own cache or deduplicate IPs before calling this tool. The _meta field
reports api_calls_made and from_cache counts.

Input parameters:

- `ips` (array, required): Public IP addresses to query, IPv4 or IPv6, e.g. ["8.8.8.8", "2001:4860:4860::8888"]. Private, loopback, reserved, multicast, and bogon addresses are rejected: they are reported under validation_erro…
- `page` (integer): Page of the result set to return, 1-based. Values below 1 are clamped to 1, and a page past the last one returns no results.
- `page_size` (integer): How many IPs to resolve and return per page. Clamped to a maximum of 1000, the API batch limit. Only the IPs on the requested page are fetched, so a smaller page size consumes less quota per call.

Output parameters:

- `result`

### `ipinfo_check_residential_proxy` (~346 tokens)

Check whether IP addresses are known residential proxies.

Returns whether each IP is a residential proxy and, if so, the proxy service name,
the date it was last seen, and the percentage of days the IP was observed as a proxy.

Requires a paid API token with residential proxy access. Results are paginated.

If the API reports an error for specific IPs, those IPs are listed in errors
with the reason and left out of results. Do not treat a missing result as
"not a residential proxy": check errors.

Results are cached in memory for the session, so repeat checks of the same IP
are served from cache without consuming API quota. You do not need to maintain
your own cache or deduplicate IPs before calling this tool. The _meta field
reports api_calls_made and from_cache counts.

Input parameters:

- `ips` (array, required): Public IP addresses to query, IPv4 or IPv6, e.g. ["8.8.8.8", "2001:4860:4860::8888"]. Private, loopback, reserved, multicast, and bogon addresses are rejected: they are reported under validation_erro…
- `page` (integer): Page of the result set to return, 1-based. Values below 1 are clamped to 1, and a page past the last one returns no results.
- `page_size` (integer): How many IPs to resolve and return per page. Clamped to a maximum of 1000, the API batch limit. Only the IPs on the requested page are fetched, so a smaller page size consumes less quota per call.

Output parameters:

- `result`

### `ipinfo_geolocate` (~396 tokens)

Get geographic location data for one or more IP addresses.

By default queries the IPinfo Lite endpoint, which returns country and continent.
Set detailed=True to query the full lookup endpoint, which adds city, region,
coordinates, timezone, and postal code.

Results are paginated.

If the API reports an error for specific IPs, those IPs are listed in errors
with the reason and left out of results.

Results are cached in memory for the session, so repeat lookups of the same IP
are served from cache without consuming API quota. You do not need to maintain
your own cache or deduplicate IPs before calling this tool. The _meta field
reports api_calls_made and from_cache counts.

Input parameters:

- `detailed` (boolean): Which IPinfo endpoint to query. Leave false to use the Lite endpoint, which returns country and continent only. Set to true to use the full lookup endpoint, which also returns city, region, latitude…
- `ips` (array, required): Public IP addresses to query, IPv4 or IPv6, e.g. ["8.8.8.8", "2001:4860:4860::8888"]. Private, loopback, reserved, multicast, and bogon addresses are rejected: they are reported under validation_erro…
- `page` (integer): Page of the result set to return, 1-based. Values below 1 are clamped to 1, and a page past the last one returns no results.
- `page_size` (integer): How many IPs to resolve and return per page. Clamped to a maximum of 1000, the API batch limit. Only the IPs on the requested page are fetched, so a smaller page size consumes less quota per call.

Output parameters:

- `result`

### `ipinfo_asn` (~412 tokens)

Get autonomous system (network ownership) information for IP addresses.

By default queries the IPinfo Lite endpoint, which returns ASN, name, and domain.
Set detailed=True to query the full lookup endpoint, which also includes the network type
(e.g. isp, hosting, business, education).

Results are paginated.

If the API reports an error for specific IPs, those IPs are listed in errors
with the reason and left out of results.

Results are cached in memory for the session, so repeat lookups of the same IP
are served from cache without consuming API quota. You do not need to maintain
your own cache or deduplicate IPs before calling this tool. The _meta field
reports api_calls_made and from_cache counts.

Input parameters:

- `detailed` (boolean): Which IPinfo endpoint to query. Leave false to use the Lite endpoint, which returns the ASN, name, and domain. Set to true to use the full lookup endpoint, which also returns the network type (isp, h…
- `ips` (array, required): Public IP addresses to query, IPv4 or IPv6, e.g. ["8.8.8.8", "2001:4860:4860::8888"]. Private, loopback, reserved, multicast, and bogon addresses are rejected: they are reported under validation_erro…
- `page` (integer): Page of the result set to return, 1-based. Values below 1 are clamped to 1, and a page past the last one returns no results.
- `page_size` (integer): How many IPs to resolve and return per page. Clamped to a maximum of 1000, the API batch limit. Only the IPs on the requested page are fetched, so a smaller page size consumes less quota per call.

Output parameters:

- `result`

### `ipinfo_quota` (~37 tokens)

Check your IPinfo API usage and remaining quota.

Returns daily and monthly request counts, the plan limit,
and how many requests remain.

Output parameters:

- `result`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ipinfo-mcp/mcp#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 65

## Common questions

### What is the IPinfo MCP server?

IPinfo is an MCP server listed in the public MCP registry as io.github.ipinfo/mcp. Official IPinfo MCP Server - IP intelligence tools for AI assistants. This page covers its hosted endpoint (https://mcp.ipinfo.io/).

### Is the IPinfo MCP server safe to use?

IPinfo scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the IPinfo MCP server expose?

IPinfo exposes 6 tools: ipinfo_lookup, ipinfo_check_privacy, ipinfo_check_residential_proxy, ipinfo_geolocate, ipinfo_asn, ipinfo_quota. Their descriptions and schemas cost roughly 1,975 tokens of context every time the server is loaded.

### Does the IPinfo MCP server require authentication?

No. We connected to IPinfo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IPinfo MCP server still maintained?

IPinfo is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.ipinfo.io/
- Authorisation metadata: https://mcp.ipinfo.io/.well-known/oauth-protected-resource
- Repository: https://github.com/ipinfo/mcp
- Website: https://ipinfo.io/
- Changelog RSS feed: https://verifymcp.io/servers/ipinfo-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ipinfo-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ipinfo-mcp/mcp