Remote MCP · Endpoint

ShiftSum Time Card MCP server

No. ShiftSum Time Card answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/time-card
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
329 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A time card calculator for hours worked.
Listing
From the official MCP registry (active).
Recent checks of ShiftSum Time Card
CheckedResultHandshake
44 minutes agoHandshake completed329 ms
3 days agoHandshake completed54 ms
13 days agoHandshake completed541 ms
13 days agoHandshake completed454 ms
15 days agoHandshake completed684 ms
15 days agoHandshake completed495 ms
17 days agoHandshake completed359 ms
18 days agoHandshake completed449 ms
18 days agoHandshake completed55 ms
20 days agoHandshake completed615 ms
22 days agoHandshake completed284 ms
25 days agoHandshake completed303 ms
27 days agoHandshake completed273 ms

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

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