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
470 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 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 completed470 ms
2 days agoHandshake completed163 ms
4 days agoHandshake completed169 ms
6 days agoHandshake completed243 ms
7 days agoHandshake completed440 ms
9 days agoHandshake completed474 ms
10 days agoHandshake completed426 ms
11 days agoHandshake completed169 ms
14 days agoHandshake completed153 ms
15 days agoHandshake completed138 ms
17 days agoHandshake completed197 ms
18 days agoHandshake completed135 ms
19 days agoHandshake completed137 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed134 ms
22 days agoHandshake completed131 ms
23 days agoHandshake completed451 ms
24 days agoHandshake completed802 ms

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

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.