IPinfo
REMOTE · MCP.IPINFO.IO · 2 COMPONENTS
Official IPinfo MCP Server - IP intelligence tools for AI assistants
Available components
Last scanned (11 hours ago)
Scores higher than 15% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security81
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 24 Oct 26 −47
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Oct 26 0
- Server version: 4.0.9 → 4.1.1 functional
- 10 Oct 26 +2
- Stability: 0.87 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- The server now declares the “logging” capability functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 3.1.1 → 4.0.9 functional
- Tool “ipinfo_lookup” changed its title: Ipinfo Lookup cosmetic
- Tool “ipinfo_quota” changed its title: Ipinfo Quota cosmetic
- Tool “ipinfo_asn” changed its title: Ipinfo Asn cosmetic
- Tool “ipinfo_check_privacy” changed its title: Ipinfo Check Privacy cosmetic
- Tool “ipinfo_check_residential_proxy” changed its title: Ipinfo Check Residential Proxy cosmetic
- Tool “ipinfo_geolocate” changed its title: Ipinfo Geolocate cosmetic
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 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 | 30 Oct 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | 6c2069f7fef37d44efffb68d922064ef186 |
| 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. | DS published | 38690 | 8 | Verified |
| ipinfo.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.ipinfo.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.ipinfo.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.ipinfo.io/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.ipinfo.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.ipinfo.io/ |
| Authorisation server | https://ipinfo.io |
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/ | Auth required | 401 | |
| http (plaintext) | http://mcp.ipinfo.io/ | Served over HTTP | 200 |
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 →
ipinfo_asn 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
ipinfo_check_privacy 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ips | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
ipinfo_check_residential_proxy 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ips | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
ipinfo_geolocate 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
ipinfo_lookup 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
ipinfo_quota 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
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
claude mcp add --transport http ipinfo-mcp 'https://mcp.ipinfo.io/'
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 32 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?
Yes. IPinfo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the IPinfo MCP server still maintained?
IPinfo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the IPinfo MCP server?
VerifyMCP ran 5 checks on IPinfo, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about IPinfo: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.