Skip to main content
Glama
iplocate

IPLocate

Official
by iplocate

Look up IP Address Network (ASN)

lookup_ip_address_network

Retrieve network and ASN details for IP addresses, including operator, route, and registry information. Supports IPv4, IPv6, or your current IP.

Instructions

Get network and ASN (Autonomous System Number) information for an IP address including the network operator, route, and regional registry. Can look up any IPv4 or IPv6 address, or your own IP if no address is provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address to look up. If not provided, returns information about the caller's IP address.

Implementation Reference

  • The handler function for the 'lookup_ip_address_network' tool. It validates the optional IP input, fetches IP data using the shared fetchIPData helper, extracts network-related fields (ip, network, asn), and returns a JSON-formatted text response or error.
    async ({ ip }) => {
      if (ip && !isValidIP(ip)) {
        return {
          content: [{
            type: "text",
            text: `Error: "${ip}" is not a valid IPv4 or IPv6 address.`
          }],
          isError: true
        };
      }
    
      try {
        const data = await fetchIPData(ip);
        const networkData = {
          ip: data.ip,
          network: data.network,
          asn: data.asn
        };
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify(networkData, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • Input schema definition used by the tool for validating the optional 'ip' parameter.
    const IPAddressSchema = {
      ip: z.string().optional().describe("IPv4 or IPv6 address to look up. If not provided, returns information about the caller's IP address.")
    };
  • src/index.ts:238-280 (registration)
    Registration of the 'lookup_ip_address_network' tool on the MCP server, including name, metadata (title, description), input schema reference, and inline handler function.
    server.registerTool(
      "lookup_ip_address_network",
      {
        title: "Look up IP Address Network (ASN)",
        description: "Get network and ASN (Autonomous System Number) information for an IP address including the network operator, route, and regional registry. Can look up any IPv4 or IPv6 address, or your own IP if no address is provided.",
        inputSchema: IPAddressSchema
      },
      async ({ ip }) => {
        if (ip && !isValidIP(ip)) {
          return {
            content: [{
              type: "text",
              text: `Error: "${ip}" is not a valid IPv4 or IPv6 address.`
            }],
            isError: true
          };
        }
    
        try {
          const data = await fetchIPData(ip);
          const networkData = {
            ip: data.ip,
            network: data.network,
            asn: data.asn
          };
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(networkData, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Shared helper function to fetch IP geolocation data from the iplocate.io API, used by all IP lookup tools including this one.
    async function fetchIPData(ip?: string): Promise<IPLocateResponse> {
      const baseUrl = "https://iplocate.io/api/lookup";
      const apiKey = process.env.IPLOCATE_API_KEY;
    
      let url = ip ? `${baseUrl}/${ip}` : `${baseUrl}/`;
    
      // Add API key if available
      if (apiKey) {
        url += `?apikey=${apiKey}`;
      }
    
      try {
        const response = await fetch(url, {
          headers: {
            'User-Agent': `mcp-server-iplocate/${VERSION}`
          }
        });
    
        if (!response.ok) {
          const errorText = await response.text();
          let errorMessage = `API request failed with status ${response.status}`;
    
          try {
            const errorJson = JSON.parse(errorText);
            if (errorJson.error) {
              errorMessage = errorJson.error;
            }
          } catch {
            // If not JSON, use the raw text
            if (errorText) {
              errorMessage = errorText;
            }
          }
    
          throw new Error(errorMessage);
        }
    
        const data = await response.json() as IPLocateResponse;
        return data;
      } catch (error) {
        if (error instanceof Error) {
          throw error;
        }
        throw new Error(`Failed to fetch IP data: ${String(error)}`);
      }
    }
  • TypeScript interface defining the structure of the IPLocate API response, which includes the 'network' and 'asn' fields extracted by this tool's handler.
    export interface IPLocateResponse {
      ip: string;
      country?: string | null;
      country_code?: string | null;
      is_eu?: boolean;
      city?: string | null;
      continent?: string | null;
      latitude?: number | null;
      longitude?: number | null;
      time_zone?: string | null;
      postal_code?: string | null;
      subdivision?: string | null;
      currency_code?: string | null;
      calling_code?: string | null;
      network?: string | null;
      asn?: ASNInfo | null;
      privacy?: PrivacyInfo;
      company?: CompanyInfo | null;
      hosting?: HostingInfo | null;
      abuse?: AbuseInfo | null;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully describes the default behavior when no IP is provided (returns caller's IP info) and specifies what information is included. However, it doesn't mention rate limits, authentication requirements, error conditions, or response format details that would be valuable for an agent.

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

Conciseness5/5

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

The description is perfectly concise with two sentences that each earn their place. The first sentence states the purpose and scope, while the second explains the parameter behavior. There's zero wasted language and it's front-loaded with the most important information.

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

Completeness3/5

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

For a single-parameter lookup tool with no annotations and no output schema, the description provides adequate basic information about what the tool does and parameter behavior. However, it doesn't describe the response structure or format, which would be important for an agent to understand what to expect from the tool.

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 description coverage is 100%, so the schema already documents the single parameter. The description adds valuable context by explaining the optional nature of the parameter and the default behavior when omitted, which goes beyond the schema's technical specification.

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 clearly states the specific action ('Get network and ASN information'), the resource ('for an IP address'), and distinguishes from siblings by specifying the exact data returned (network operator, route, regional registry). It explicitly mentions both IPv4 and IPv6 addresses, making the scope unambiguous.

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?

The description provides clear context about when to use this tool (for network/ASN info) and distinguishes it from siblings by specifying the type of information returned. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools for different information needs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iplocate/mcp-server-iplocate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server