Remote MCP · Endpoint

io.github.theluckystrike/timesheets MCP server

No. io.github.theluckystrike/timesheets answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://mcp.zovo.one/mcp/timesheets

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/timesheets
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/timesheets
CheckedResultHandshake
56 minutes agoHandshake completed49 ms
3 days agoHandshake completed32 ms
12 days agoHandshake completed68 ms
13 days agoHandshake completed22 ms
15 days agoHandshake completed50 ms
15 days agoHandshake completed21 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed594 ms
18 days agoHandshake completed612 ms
20 days agoHandshake completed610 ms
22 days agoHandshake completed911 ms
25 days agoHandshake completed506 ms
27 days agoHandshake completed62 ms

The last 13 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 io.github.theluckystrike/timesheets and makes no claim about it beyond what these checks measured.