Skip to main content
Glama
IPGeolocation

IPGeolocation MCP Server

by IPGeolocation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Company/Organization Lookup

lookup_company
Read-only

Read-only ownership lookup via GET /v3/ipgeo. Company details require a paid plan; free plans return basic ASN ownership only. Cost: 1 credit.

Instructions

Read-only ownership lookup via GET /v3/ipgeo. Company details require a paid plan; free plans return basic ASN ownership only. Cost: 1 credit. This response is limited to company and ASN ownership; lookup_ip can return ownership together with location, security, abuse, network, timezone, or currency.

Returns { company, asn }: company name/type/domain plus ASN allocation fields when available. ip omitted means the server's public egress IP. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address to look up. Omit to check the server's public egress IP.
force_refreshNoDefault false. When true, bypasses cached ownership data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

NameRequiredDescriptionDefault
dataNoPresent on success: API result after field selection, redaction, and transport limits.
pageNo
errorNoPresent on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.3
    • 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"
+]
  2. Changed3 schema fields changedv2.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / ip / description
      Previous value: -"IPv4 or IPv6 address to look up. Omit to check the caller's IP."New value: +"IPv4 or IPv6 address to look up. Omit to check the server's public egress IP."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {
+        "anyOf": [
+          {
+            "type": "null"
+          },
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "string"
+          },
+          {
+            "type": "array"
+          },
+          {
+            "type": "object"
+          }
+        ]
+      },
+      "description": "Present on success: API result after field selection, redaction, and transport limits.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": false,
+      "description": "Present on failure, with isError: true.",
+      "properties": {
+        "assistant_guidance": {
+          "type": "string"
+        },
+        "category": {
+          "type": "string"
+        },
+        "documented_status": {
+          "type": "boolean"
+        },
+        "explanation_hint": {
+          "type": "string"
+        },
+        "guidance": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "source": {
+          "enum": [
+            "mcp_server",
+            "ipgeolocation_api"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "source",
+        "category",
+        "message",
+        "retryable",
+        "guidance",
+        "assistant_guidance"
+      ],
+      "type": "object"
+    },
+    "page": {
+      "additionalProperties": false,
+      "properties": {
+        "cursor": {
+          "description": "Opaque cursor returned in page.cursor or page.next_cursor. Retrieval requires the same server process and API key and does not repeat the original lookup.",
+          "maxLength": 80,
+          "pattern": "^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}:\\d{1,16}$",
+          "type": "string"
+        },
+        "expires_at": {
+          "description": "ISO timestamp for idle expiry. Successful page reads extend the cache TTL; eviction or process restart can also remove the result.",
+          "type": "string"
+        },
+        "format": {
+          "const": "structuredContent_json",
+          "type": "string"
+        },
+        "json_fragment": {
+          "description": "JSON fragment of the original structuredContent. Fragments concatenate in offset order into the complete JSON, including bulk items and errors.",
+          "type": "string"
+        },
+        "next_cursor": {
+          "description": "Cursor for the next get_cached_result page, absent on the last page. Page reads never call the API or consume credits.",
+          "maxLength": 80,
+          "pattern": "^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}:\\d{1,16}$",
+          "type": "string"
+        },
+        "offset": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "source_tool": {
+          "type": "string"
+        },
+        "total_chars": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "source_tool",
+        "format",
+        "json_fragment",
+        "offset",
+        "total_chars",
+        "cursor",
+        "expires_at"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. Changed2 schema fields changedv2.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Set true only when the user asks to refresh cached ownership data; a successful refresh makes a new upstream request and can consume credits."New value: +"Default false. When true, bypasses cached ownership data; a successful refresh makes a new upstream request and can consume credits."
  4. Changed1 schema field changedv1.0.15
    • 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 ownership data; a successful refresh makes a new upstream request and can consume credits."
  5. First observedv1.0.10

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context: credit cost per call, the paid-plan gating that degrades results on free plans, caching behavior, and the fact that force_refresh makes a new upstream request that can consume credits. That is exactly the kind of cost/side-effect disclosure annotations cannot carry.

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?

Content is front-loaded with the purpose, then constraints, then the sibling differentiation, then return shape — a sensible ordering. It is slightly dense, and the return-shape sentence partially duplicates the output schema, but every sentence still carries usable information.

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?

For a zero-required-parameter lookup with an output schema present, the description covers purpose, cost, plan gating, caching side effects, and a summary of the returned { company, asn } shape. Nothing an agent needs in order to call it correctly is missing.

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 both parameters are already fully documented, including the omitted-ip egress behavior and the force_refresh credit caveat. The description restates these facts rather than adding syntax or edge cases beyond the schema, so the baseline 3 applies.

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 ownership lookup) and names the endpoint (GET /v3/ipgeo). It explicitly contrasts itself with lookup_ip, so the agent can distinguish 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 Guidelines5/5

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

Names the alternative (lookup_ip) and the condition that selects it — when ownership is needed together with location, security, abuse, network, timezone, or currency. It also states the plan prerequisite (paid plan for company details, free plans get ASN ownership only) and the 1-credit cost, so an agent knows both when to call it and what constraints apply.

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

Deploy Server

Other Tools