Remote MCP · Endpoint

io.github.mcpcentral-io/mcp-time MCP server

No. io.github.mcpcentral-io/mcp-time answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.time.mcpcentral.io/

The last check completed an MCP handshake.

Registry name
io.github.mcpcentral-io/mcp-time
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
418 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Time MCP server via HTTP
Repository
https://github.com/mcpcentral-io/mcp-time
Listing
From the official MCP registry (active).
Recent checks of io.github.mcpcentral-io/mcp-time
CheckedResultHandshake
1 hour agoHandshake completed418 ms
1 day agoHandshake completed340 ms
2 days agoHandshake completed362 ms
3 days agoHandshake completed378 ms
4 days agoHandshake completed265 ms
5 days agoHandshake completed341 ms
6 days agoHandshake completed514 ms
9 days agoHandshake completed378 ms
11 days agoHandshake completed453 ms
14 days agoHandshake completed395 ms
16 days agoHandshake completed92 ms
18 days agoHandshake completed208 ms
20 days agoHandshake completed339 ms
22 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
27 days agoCredentials required—
29 days agoCredentials required—

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.mcpcentral-io/mcp-time and makes no claim about it beyond what these checks measured.