Remote MCP · Endpoint
Ip Geolocation Mcp MCP server
No. Ip Geolocation Mcp answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://ip-geolocation-mcp.mcpize.run/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.varvararatta/ip_geolocation_mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 518 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Unlock the power of IP geolocation with our tool! Whether you're a developer needing location data
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 518 ms |
| 1 day ago | Handshake completed | 103 ms |
| 3 days ago | Handshake completed | 179 ms |
| 3 days ago | Handshake completed | 152 ms |
| 4 days ago | Handshake completed | 114 ms |
| 5 days ago | Handshake completed | 111 ms |
| 7 days ago | Handshake completed | 313 ms |
| 10 days ago | Handshake completed | 625 ms |
| 12 days ago | Handshake completed | 474 ms |
| 15 days ago | Handshake completed | 626 ms |
| 17 days ago | Handshake completed | 675 ms |
| 19 days ago | Handshake completed | 592 ms |
| 21 days ago | Handshake completed | 598 ms |
| 23 days ago | Handshake completed | 714 ms |
| 25 days ago | Handshake completed | 497 ms |
| 26 days ago | Handshake completed | 563 ms |
| 28 days ago | Handshake completed | 666 ms |
| 29 days ago | Handshake completed | 620 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Ip Geolocation Mcp and makes no claim about it beyond what these checks measured.