IPGeolocation MCP Server

ASN Details

lookup_asn

Read-only

Read-only ASN enrichment via GET /v3/asn. Paid only. Cost: 1 credit. Queries accept asn or ip, with asn taking priority. The response covers ASN relationships, route prefixes, allocation details, and WHOIS; lookup_ip provides basic ASN…

Instructions

Returns { asn } core fields plus included peers, downstreams, upstreams, routes, or whois_response. include accepts those five values. fields/excludes accept full asn.* paths or root-relative paths such as upstreams.as_number. fields automatically enables required optional datasets; excludes alone never requests extra datasets. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

Input Schema

Name	Required	Description
`ip`	No	IPv4 or IPv6 address to find the ASN for. Used only if asn is not provided.
`asn`	No	AS number to look up (e.g. AS13335 or just 13335). Takes priority over ip if both are provided.
`fields`	No	Comma-separated dot-path fields to return (e.g. asn.as_number,asn.organization or upstreams.as_number). Paths can be full (asn.upstreams.as_number) or relative to the asn root (upstreams.as_number). This server auto-adds optional datasets referenced by fields; excludes alone does not enable them.
`include`	No	Comma-separated extra data to include: peers, downstreams, upstreams, routes, whois_response. No additional credit cost.
`excludes`	No	Comma-separated dot-path fields to exclude (e.g. asn.date_allocated,asn.rir or upstreams.description). Paths can be full or relative to the asn root.
`force_refresh`	No	Default false. When true, bypasses cached ASN data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

Name	Required	Description
`data`	No	Present on success: API result after field selection, redaction, and transport limits.
`page`	No
`error`	No	Present on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.3Oct 28, 2026

removedOutput schema / properties / data / additionalProperties / anyOf

Removed value: -[
-  {
-    "type": "null"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "object"
-  }
-]

addedOutput schema / properties / data / additionalProperties / type

Added value: +[
+  "null",
+  "boolean",
+  "number",
+  "string",
+  "array",
+  "object"
+]

Addedv2.0.1Oct 13, 2026
Removedv2.0.0Jul 25, 2026

Changed1 schema field changedv1.0.15May 8, 2026

changedInput schema / properties / force_refresh / description

Previous value: -"Default false. Leave unset unless the user asks to refresh or rerun."New value: +"Default false. Set true only when the user asks to refresh cached ASN data; a successful refresh makes a new upstream request and can consume credits."

First observedv1.0.10Mar 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing that the tool is paid, costs 1 credit, that force_refresh issues a new upstream request and can consume additional credits, and that cached data is bypassed. It also documents the non-obvious interaction where fields auto-enables optional datasets but excludes does not.

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?

Front-loaded with cost and access constraints, then inputs, then output shape — a sensible order. The return-shape sentence is somewhat dense and partially redundant given an output schema exists, but no sentence is pure filler.

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

Completeness4/5

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

Covers cost, caching, input precedence, dataset inclusion rules, and result fields for a zero-required-parameter enrichment tool. The enumeration of response fields is largely redundant with the existing output schema, so it is complete but not maximally efficient.

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

Parameters4/5

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

Schema coverage is 100%, so per-parameter meaning is already covered; the description's added value is the cross-parameter rule that fields implicitly requests datasets while excludes never does, plus the asn-over-ip priority. That is real semantics beyond the schema, though much of the rest restates it.

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?

States a specific verb and resource ('Read-only ASN enrichment via GET /v3/asn') and immediately scopes it against the nearest sibling by noting that lookup_ip returns basic ASN data plus geolocation. An agent can pick between the two without opening either schema.

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

Usage Guidelines4/5

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

Names the alternative (lookup_ip) and the tradeoff that selects it, and clarifies precedence between the asn and ip inputs. It stops short of an explicit 'do not use this when…' exclusion, but the routing context is clear.

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

Deploy Server