Remote MCP · Endpoint

McpStamp Leave Tracker MCP server

No. McpStamp Leave Tracker answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.zovo.one/mcp/leave

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/leave
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Employee leave and PTO: requests, approvals, balances, who is out, and conflict checks.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Leave Tracker
CheckedResultHandshake
20 minutes agoHandshake completed50 ms
8 days agoHandshake completed240 ms
9 days agoHandshake completed42 ms
11 days agoHandshake completed81 ms
12 days agoHandshake completed120 ms
13 days agoHandshake completed843 ms
14 days agoHandshake completed589 ms
15 days agoHandshake completed945 ms
16 days agoHandshake completed112 ms
19 days agoHandshake completed29 ms
21 days agoHandshake completed150 ms
24 days agoHandshake completed157 ms
26 days agoHandshake completed595 ms
28 days agoHandshake completed550 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 Leave Tracker and makes no claim about it beyond what these checks measured.