Skip to content

IPinfo MCP server

io.github.ipinfo/mcpipinfostreamable-httpv0.3.2Scanned

Official IPinfo MCP Server - IP intelligence tools for AI assistants

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the IPinfo MCP server can do

The IPinfo MCP server is published by the GitHub account ipinfo. It has 6 tools. It can create or change data (3 tools: ipinfo_check_privacy, ipinfo_check_residential_proxy and ipinfo_quota), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Oct 22, 2026, version 0.3.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • ipinfo_check_privacyCheck whether IP addresses are using privacy or anonymity services.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • ipinfo_check_residential_proxyCheck whether IP addresses are known residential proxies.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • ipinfo_quotaCheck your IPinfo API usage and remaining quota.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check your IPinfo API usage and remaining quota. Returns daily and monthly request counts, the plan limit, and how many requests remain.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 3Show 3 read-only tools
  • ipinfo_asnGet autonomous system (network ownership) information for IP addresses.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • ipinfo_geolocateGet geographic location data for one or more IP addresses.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • ipinfo_lookupLook up geolocation, network, and metadata for one or more IP addresses.No findings

    Why it is in this group

    • The name "ipinfo_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://mcp.ipinfo.io/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://mcp.ipinfo.io/.well-known/oauth-protected-resource
Authorization servers
https://ipinfo.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.ipinfo.io/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://mcp.ipinfo.io/.well-known/oauth-protected-resource
    • Authorization servers: none to https://ipinfo.io
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.ipinfo.io/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://mcp.ipinfo.io/.well-known/oauth-protected-resource
    • Authorization servers: none to https://ipinfo.io
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

Pinned to version 0.3.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ipinfo__ipinfo_lookup",
      "mcp__ipinfo__ipinfo_geolocate",
      "mcp__ipinfo__ipinfo_asn"
    ],
    "ask": [
      "mcp__ipinfo__ipinfo_check_privacy",
      "mcp__ipinfo__ipinfo_check_residential_proxy",
      "mcp__ipinfo__ipinfo_quota"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ipinfo. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ipinfo/mcp/verify?hash=21870a2184bfe071de59fdb74cd8bed9370106f67bf18f632a8a2d9491c96206" | jq -e '.changed == false'

Pinned hash 21870a2184bf, from Oct 22, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ipinfo/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ipinfo/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ipinfo/mcp.svg)](https://radar.anlyon.com/servers/io.github.ipinfo/mcp)

Source: MCP Registry · repository. Synced Nov 13, 2026, 14:17 UTC.

IPinfo MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the IPinfo MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the IPinfo MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the IPinfo MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the IPinfo MCP server have?

6 tools: 3 write, 3 read. ipinfo_check_privacy, ipinfo_check_residential_proxy, ipinfo_quota, ipinfo_lookup, ipinfo_geolocate and ipinfo_asn.

Does the IPinfo MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the IPinfo MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the IPinfo MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 22, 2026.