Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IPinfo

REMOTE · MCP.IPINFO.IO · 2 COMPONENTS · SCANNED SEP 21

Official IPinfo MCP Server - IP intelligence tools for AI assistants

Available components

remote · mcp.ipinfo.io 71 pypi · ipinfo-mcp-server 36
+3 this week 71 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

remote · mcp.ipinfo.io

# add to Claude Code
claude mcp add --transport http ipinfo-mcp 'https://mcp.ipinfo.io/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ipinfo-mcp": {
      "url": "https://mcp.ipinfo.io/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ipinfo-mcp": {
      "type": "http",
      "url": "https://mcp.ipinfo.io/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ipinfo-mcp --url 'https://mcp.ipinfo.io/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ipinfo-mcp:
    url: "https://mcp.ipinfo.io/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ipinfo-mcp": {
      "Transport": "http",
      "Url": "https://mcp.ipinfo.io/"
    }
  }
}
# add to Vellum
assistant mcp add ipinfo-mcp -t streamable-http -u 'https://mcp.ipinfo.io/'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +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.

  • 19 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 10 Sept 26 +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.

  • 9 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://mcp.ipinfo.io/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ipinfo.io CN=YR1,O=Let's Encrypt,C=US 15 Sept 2026 14 Dec 2026 RSA 2048 SHA256-RSA 682461056129dc8d854c1f7896492e03256
SANs: *.api.ipinfo.io, *.ipinfo.io, ipinfo.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ipinfo.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
ipinfo.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ipinfo.io/ Verified 200
http (plaintext) http://mcp.ipinfo.io/ Served over HTTP 200
MCP tools · 6 exposed · ~1,975 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ipinfo_asn ~412

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.

NameTypeReqDescription
detailedboolean–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…
ipsarrayyesPublic 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…
pageinteger–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_sizeinteger–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.
NameTypeReqDescription
result–yes–

No examples provided.

ipinfo_check_privacy ~344

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.

NameTypeReqDescription
ipsarrayyesPublic 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…
pageinteger–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_sizeinteger–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.
NameTypeReqDescription
result–yes–

No examples provided.

ipinfo_check_residential_proxy ~346

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.

NameTypeReqDescription
ipsarrayyesPublic 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…
pageinteger–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_sizeinteger–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.
NameTypeReqDescription
result–yes–

No examples provided.

ipinfo_geolocate ~396

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.

NameTypeReqDescription
detailedboolean–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…
ipsarrayyesPublic 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…
pageinteger–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_sizeinteger–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.
NameTypeReqDescription
result–yes–

No examples provided.

ipinfo_lookup ~440

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.

NameTypeReqDescription
detailedboolean–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…
ipsarrayyesPublic 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…
pageinteger–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_sizeinteger–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.
NameTypeReqDescription
result–yes–

No examples provided.

ipinfo_quota ~37

Check your IPinfo API usage and remaining quota. Returns daily and monthly request counts, the plan limit, and how many requests remain.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

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.