mcp-ip2location
https://mcp.ip2location.io/mcp ↗
Description
# IP2Location.io MCP server This is a simple Model Context Protocol (MCP) server implementation for IP2Location.io API. It will return a detailed geolocation information for any given IPv4 or IPv6 address. # Features - **Comprehensive Geolocation Data**: Retrieves a wide range of information, including country, region, city, latitude, longitude, ZIP code, time zone, and more. - **Network Details**: Provides network-related data such as ASN, ISP, domain, and network speed. - **Security Insights**: Detects proxy information, including proxy type and provider. - **Simple Integration**: Built as a `FastMCP` tool, allowing for easy integration into compatible systems. - **Asynchronous**: Utilizes `httpx` for non-blocking asynchronous API requests. # Requirement This MCP server requires a API key. You can [sign up](https://www.ip2location.io/sign-up) for a free API key and enjoy up to 50,000 queries per month for free.
What our measurements say
mcp-ip2location is a remote MCP server published at mcp.ip2location.io. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 247 ms, placing it among the faster endpoints. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool name 'get_geolocation' clearly indicates its purpose.
Weaknesses
- Description is incomplete and cut off mid-sentence.
- Input schema and parameter details are missing.
- Critical batching instruction is ambiguous without full context.
get_geolocation— Description is incomplete and cut off mid-sentence.get_geolocation— Input schema and parameter details are missing.
Verdict
Event narrative
Risk: medium
- 2026-09-11T05:44:28.819Z — Era changed from 'auth-gated' to 'legacy' · Agent now operates under legacy access controls
- 2026-09-11T05:44:28.819Z — Compliance score set to 100 from null · Indicates full compliance achieved
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 61ms → warm 42ms (penalty 19ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/support-0cin-mcp-ip2location)<a href="https://mcpmetrics.io/servers/support-0cin-mcp-ip2location"><img src="https://mcpmetrics.io/badge/support-0cin/mcp-ip2location/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see