IPGeolocation MCP Server

Get My IP Address

get_my_ip

Read-only

Retrieve the public IP address of the machine hosting your MCP server. Use it to identify your external IP without API keys or input parameters.

Instructions

Returns the public IP address of the machine running this MCP server via GET /v3/getip. Takes no input parameters and requires no API key, account, or credits. The response is a plain IP address string, not geolocation data; lookup_ip provides location, ASN, timezone, currency, security, and abuse data.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ip`	No
`page`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.1Oct 13, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "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"
+    },
+    "ip": {
+      "type": "string"
+    },
+    "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"
+}

First observedv1.0.10Mar 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes beyond the readOnlyHint/openWorldHint annotations by disclosing that no API key, account, or credits are required – auth/billing context an agent cannot infer from annotations – and by specifying the response is a plain IP string. It does not cover rate limits or failure modes, but the added auth and response-shape detail is real value.

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?

Three sentences that each carry a distinct payload: what it returns, what it costs/requires, and how it differs from the nearest alternative. Purpose is front-loaded and nothing is padding.

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-argument, read-only lookup with an output schema, the description supplies everything an agent needs: identity of the resource, absence of required credentials, return shape, and sibling routing. No behavioral dimension is left unaddressed.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing further to document. The description reinforces this with 'takes no input parameters,' which matches additionalProperties: false in the schema.

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+resource ('Returns the public IP address of the machine running this MCP server') and even names the underlying route GET /v3/getip. It explicitly distinguishes itself from sibling lookup_ip by scope, so an agent can separate 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?

Gives the selecting condition directly: use this for the caller's own public IP; use lookup_ip when location, ASN, timezone, currency, security, or abuse data is needed. It also pre-empts a false assumption by stating the result is not geolocation, which is the main reason an agent would pick the wrong sibling.

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

Deploy Server