OnlineCyberTools MCP (280+ filterable tools)

network_ip_geolocation

Read-only

Resolve any public IPv4 or IPv6 address to its geographic location and network owner including country, city, coordinates, ISP, and ASN. Flags proxy, hosting, and mobile connections.

Instructions

IP Geolocation Lookup. Resolve a single public IPv4 or IPv6 address to its geographic location and network owner by querying the external ip-api.com geolocation service (MaxMind GeoLite2). Use this when you have an IP and need its country, city, coordinates, ISP/ASN, and proxy/hosting/mobile flags; use network_my_ip instead to geolocate the caller's own public IP with no input. Read-only and non-destructive, but it makes an outbound network request, so results depend on live third-party data and may vary between calls. Rejects private/reserved IPs (10.x, 172.16-31.x, 192.168.x, 127.x). Rate-limited (10 req/min, 300/day anonymous; CAPTCHA above 30/hr). Returns nested location, network, accuracy, and data_sources objects.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ip`	Yes	Public IPv4 or IPv6 address to locate. Must be a valid, non-private, non-reserved address.
`worker_id`	No	Optional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when the lookup succeeded.
`ip`	No	The IP address that was looked up, echoed back.
`location`	No	Geographic data for the IP.
`network`	No	Network ownership and classification for the IP.
`accuracy`	No	Static confidence estimates for each location tier.
`data_sources`	No	Provenance of each data category.
`timestamp`	No	ISO 8601 timestamp of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.1Jun 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / ip

Added value: +{
+  "description": "Public IPv4 or IPv6 address to locate. Must be a valid, non-private, non-reserved address.",
+  "examples": [
+    "8.8.8.8"
+  ],
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "ip"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accuracy": {
+      "description": "Static confidence estimates for each location tier.",
+      "properties": {
+        "city": {
+          "description": "City-level accuracy estimate.",
+          "type": "string"
+        },
+        "coordinates": {
+          "description": "Coordinate precision estimate.",
+          "type": "string"
+        },
+        "country": {
+          "description": "Country-level accuracy estimate.",
+          "type": "string"
+        },
+        "note": {
+          "description": "Caveat about accuracy variance.",
+          "type": "string"
+        },
+        "region": {
+          "description": "Region-level accuracy estimate.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "data_sources": {
+      "description": "Provenance of each data category.",
+      "properties": {
+        "geolocation": {
+          "description": "Source of the geolocation data.",
+          "type": "string"
+        },
+        "isp_info": {
+          "description": "Source of the ISP/owner data.",
+          "type": "string"
+        },
+        "network_info": {
+          "description": "Source of the routing/network data.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ip": {
+      "description": "The IP address that was looked up, echoed back.",
+      "type": "string"
+    },
+    "location": {
+      "description": "Geographic data for the IP.",
+      "properties": {
+        "city": {
+          "description": "City name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "continent": {
+          "description": "Continent name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "continent_code": {
+          "description": "Two-letter continent code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "country": {
+          "description": "Country name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "country_code": {
+          "description": "ISO 3166-1 alpha-2 country code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "currency": {
+          "description": "Local currency code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "district": {
+          "description": "District/neighborhood, when known.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "latitude": {
+          "description": "Latitude in decimal degrees.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "longitude": {
+          "description": "Longitude in decimal degrees.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "region": {
+          "description": "Region/state name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "region_code": {
+          "description": "Region/state code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timezone": {
+          "description": "IANA timezone name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timezone_offset": {
+          "description": "UTC offset in seconds.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "zip": {
+          "description": "Postal/ZIP code.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "network": {
+      "description": "Network ownership and classification for the IP.",
+      "properties": {
+        "as_number": {
+          "description": "Autonomous System number (e.g. AS15169).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "as_organization": {
+          "description": "Autonomous System organization name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "is_hosting": {
+          "description": "True if the IP belongs to a hosting/datacenter provider.",
+          "type": "boolean"
+        },
+        "is_mobile": {
+          "description": "True if the IP is a mobile/cellular network.",
+          "type": "boolean"
+        },
+        "is_proxy": {
+          "description": "True if the IP is a known proxy/VPN/Tor exit.",
+          "type": "boolean"
+        },
+        "isp": {
+          "description": "Internet service provider name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "organization": {
+          "description": "Organization that owns the IP block.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reverse_dns": {
+          "description": "PTR/reverse-DNS hostname, when resolvable.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the lookup succeeded.",
+      "type": "boolean"
+    },
+    "timestamp": {
+      "description": "ISO 8601 timestamp of the response.",
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Despite annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds valuable behavioral context: outbound network request, dependency on live third-party data, rejection of private/reserved IPs, and rate limits (10 req/min, 300/day anonymous). This goes beyond the minimal annotation coverage.

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 a single dense paragraph that efficiently conveys purpose, usage, behavioral details, constraints, and output structure. Every sentence adds value with no redundancy.

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 tool's complexity (external API, rate limits, private IP validation) and the presence of an output schema, the description covers all essential aspects: what it does, how to use it, behavioral caveats, constraints, and output structure. No gaps are evident.

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 coverage is 100% with detailed descriptions for both parameters (ip and worker_id). The description adds some context (e.g., IP must be public, output objects listed) but does not significantly enhance parameter semantics beyond the schema. Baseline score of 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 clearly states the tool resolves a public IPv4 or IPv6 address to geographic location and network owner using ip-api.com. It distinguishes itself from sibling network_my_ip by specifying that this tool requires an input IP while the sibling geolocates the caller's own IP.

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?

Explicitly states when to use this tool ('when you have an IP and need its country, city, coordinates, ISP/ASN...') and when to use the alternative network_my_ip. This provides clear decision guidance.

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

Deploy Server