Skip to main content
Glama
iplocate

IPLocate

Official
by iplocate

Look up IP Address Company

lookup_ip_address_company

Find company information for any IP address, including organization name, domain, and type. Look up IPv4 or IPv6 addresses or identify your own IP's company details.

Instructions

Get company/organization information for an IP address including the company name, domain, and type of organization. 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

  • Handler function that validates the input IP address, fetches complete IP data from the API, extracts the company information, and returns it as formatted JSON or an error response.
    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 companyData = {
          ip: data.ip,
          company: data.company
        };
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify(companyData, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • src/index.ts:282-324 (registration)
    Registers the 'lookup_ip_address_company' MCP tool with the server, providing title, description, input schema, and the inline handler function.
    // Register tool: lookup_ip_address_company
    server.registerTool(
      "lookup_ip_address_company",
      {
        title: "Look up IP Address Company",
        description: "Get company/organization information for an IP address including the company name, domain, and type of organization. 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 companyData = {
            ip: data.ip,
            company: data.company
          };
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(companyData, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod-based input schema definition for the tool, defining 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.")
    };
  • Core helper function that makes the HTTP request to iplocate.io API to fetch IP data, supports API key, handles errors, and returns typed IPLocateResponse.
    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 API response, including the 'company' field used by this tool.
    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 describes the core functionality and default behavior (looking up caller's IP if none provided), but doesn't mention rate limits, authentication requirements, error conditions, or response format details. The description adds basic context but lacks comprehensive behavioral traits.

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 return data, while the second explains parameter behavior and defaults. No wasted words, and information is front-loaded appropriately.

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?

Given the tool's moderate complexity (single optional parameter, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does and parameter behavior, but doesn't describe the return format or potential limitations. For a lookup tool with no output schema, more detail about response structure would be helpful.

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 schema already fully documents the single parameter. The description mentions the same information about the parameter (IPv4/IPv6 address, default to caller's IP if not provided) but doesn't add meaningful semantic context beyond what's in the schema. This meets the baseline for high schema coverage.

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 company/organization information') and resource ('for an IP address'), including what information is returned ('company name, domain, and type of organization'). It distinguishes from sibling tools by focusing on company/organization data rather than abuse contacts, details, location, network, or privacy information.

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 on when to use this tool: for IP address company lookups, with the ability to look up any IPv4/IPv6 address or the caller's own IP if no address is provided. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, though the sibling names imply different data types.

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