IPinfo MCP Server

Official

by ipinfo

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Ipinfo Asn

ipinfo_asn

Read-onlyIdempotent

Retrieve autonomous system (ASN) and network ownership details for IPv4 or IPv6 addresses, with optional network type, pagination, and session caching.

Instructions

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 Schema

TableJSON Schema

Name	Required	Description
`ips`	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_errors and left out of results.
`page`	No	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.
`detailed`	No	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, hosting, business, education) and when the AS record last changed; it requires a token whose plan includes that data, otherwise the call fails with ACCESS_DENIED.
`page_size`	No	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 Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.13Sep 30, 2026
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
First observedv0.1.12Sep 15, 2026

TDQS

A4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, the description discloses pagination behavior, per-IP error reporting with reasons, in-memory caching and its quota implications, the _meta counters, and the ACCESS_DENIED risk for detailed lookups without the right plan. This gives an agent actionable behavioral context well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized into clear thematic paragraphs and every sentence adds useful information, such as caching, error handling, and endpoint differences. It is slightly longer than strictly needed—'Results are paginated' overlaps with the page/page_size parameters—but overall it is structured and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description is remarkably complete: it covers endpoint selection, pagination, error reporting, validation errors, quota caching, and plan limitations. An agent has everything needed to call the tool correctly and interpret its side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all four parameters thoroughly, including validation behavior, clamping, defaults, and plan requirements. The description adds context around caching and quota, but it does not materially redefine parameter semantics beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get autonomous system (network ownership) information for IP addresses.' It further clarifies the return fields (ASN, name, domain, network type), which clearly distinguishes it from siblings like ipinfo_geolocate, ipinfo_check_privacy, and ipinfo_lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does and how parameters alter endpoints, but it gives no guidance on when to choose this tool over alternatives such as ipinfo_lookup or ipinfo_check_privacy. No exclusions, comparison points, or selection conditions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server