Remote MCP · Endpoint

Location and Timezone MCP Server by RoxyAPI MCP server

No. Location and Timezone MCP Server by RoxyAPI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://roxyapi.com/mcp/location

The last check completed an MCP handshake.

Registry name
com.roxyapi/location
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
176 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
City geocoding and timezone resolution for birth data, for AI agents, one API key.
Listing
From the official MCP registry (active).
Recent checks of Location and Timezone MCP Server by RoxyAPI
CheckedResultHandshake
1 hour agoHandshake completed176 ms
10 hours agoHandshake completed205 ms
1 day agoHandshake completed151 ms
2 days agoHandshake completed146 ms
4 days agoHandshake completed173 ms
4 days agoHandshake completed496 ms
5 days agoHandshake completed141 ms
6 days agoHandshake completed163 ms
8 days agoHandshake completed237 ms
11 days agoHandshake completed161 ms
13 days agoHandshake completed170 ms
16 days agoHandshake completed464 ms
18 days agoHandshake completed441 ms
20 days agoHandshake completed470 ms
22 days agoHandshake completed163 ms
24 days agoHandshake completed169 ms
26 days agoHandshake completed243 ms
27 days agoHandshake completed440 ms
29 days agoHandshake completed474 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.

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 Location and Timezone MCP Server by RoxyAPI and makes no claim about it beyond what these checks measured.