Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_my_ip

Detect your public IP address and enrich it with geolocation, proxy/VPN status, and ASN details via ip-api.com.

Instructions

My Public IP Address and Geolocation. Detect the caller public IP address and enrich it with geolocation, proxy/VPN, and ASN details via an outbound lookup to ip-api.com. The result is live and varies by who calls it, since the IP is read from the incoming request headers (X-Forwarded-For, X-Real-IP, CF-Connecting-IP and similar) rather than from a parameter. Use this when you want the requester own address; use network_ip_geolocation instead to look up an arbitrary IP you supply. Not read-only in the side-effect sense (it queries a third party) and rate-limited (30 requests/minute for anonymous callers). Takes no input (HTTP GET, no body or query parameters). Returns the detected IP, proxy analysis, header echo, and country/region/city/ISP/ASN when the geo lookup succeeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoThe public IP address detected for the caller, or unknown if it could not be determined.
timestampNoISO 8601 time the response was generated.
sourceNoHow the IP was obtained; always server_detection.
proxy_detectionNoProxy/CDN analysis derived from forwarding headers.
ip_analysisNoPer-header breakdown keyed by server variable (HTTP_X_FORWARDED_FOR and similar); each entry reports its value, a human description, and a present flag.
countryNoCountry name from ip-api.com (present only when the geo lookup succeeds).
countryCodeNoTwo-letter ISO country code.
regionNoRegion or state name (ip-api regionName).
cityNoCity name.
zipNoPostal/ZIP code.
latNoLatitude of the approximate location.
lonNoLongitude of the approximate location.
timezoneNoIANA timezone name for the location.
ispNoInternet service provider name.
orgNoOrganization that owns the IP.
asNoAutonomous System number and name (such as AS15169 Google LLC).
mobileNoTrue if the IP is on a mobile carrier network.
proxyNoTrue if ip-api flags the IP as a proxy or VPN.
hostingNoTrue if the IP belongs to a hosting or data-center range.
headersNoEcho of selected request headers including proxy-detection headers; each value is the header string or null when absent.
data_sources_infoNoExplanations of how each data point is derived and approximate accuracy.
server_infoNoDetails about the responding server and connection (server IP/port, HTTPS, protocol, method).
warningNoPresent only when the ip-api.com lookup failed; the geo fields are then omitted.
Behavior5/5

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

Discloses that it queries a third-party API (ip-api.com), is rate-limited, reads IP from request headers, and that results are live. These details go beyond annotations, which already set readOnlyHint=false.

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?

The description is comprehensive but slightly verbose; however, each sentence adds value and it is well-structured with important details front-loaded.

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?

Covers purpose, usage, behavior, input, and expected output fields. With no parameters and rich annotations, the description is fully informative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty with additionalProperties: true, and the description explicitly says 'Takes no input (HTTP GET, no body or query parameters)', adding clarity beyond 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?

The description clearly states the tool detects the caller's public IP and enriches it with geolocation, proxy/VPN, and ASN details. It distinguishes from sibling tool 'network_ip_geolocation' by specifying when to use each.

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 (requester's own address) versus alternatives (network_ip_geolocation for arbitrary IP). Also provides context on side effects and rate limits.

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/Jambozx/onlinecybertools-mcp-server'

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