Remote MCP · Endpoint

McpStamp Time Tracker MCP server

No. McpStamp Time Tracker answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://mcp.zovo.one/mcp/time-tracker

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/time-tracker-timesheet-billable-hours
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
20 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Track billable hours: timers, timesheets, weekly totals, CSV export, unbilled hours to invoices.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Time Tracker
CheckedResultHandshake
14 minutes agoHandshake completed20 ms
9 days agoHandshake completed89 ms
9 days agoHandshake completed22 ms
11 days agoHandshake completed83 ms
12 days agoHandshake completed80 ms
13 days agoHandshake completed45 ms
14 days agoHandshake completed63 ms
15 days agoHandshake completed75 ms
16 days agoHandshake completed59 ms
19 days agoHandshake completed103 ms
22 days agoHandshake completed80 ms
24 days agoHandshake completed52 ms
26 days agoHandshake completed99 ms
28 days agoHandshake completed59 ms

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

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 McpStamp Time Tracker and makes no claim about it beyond what these checks measured.