Remote MCP · Endpoint

io.github.theluckystrike/standup MCP server

No. io.github.theluckystrike/standup answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://mcp.zovo.one/mcp/standup

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/standup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A task board for daily standups: columns, due dates, priorities, weekly review.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/standup
CheckedResultHandshake
52 minutes agoHandshake completed33 ms
3 days agoHandshake completed22 ms
12 days agoHandshake completed20 ms
13 days agoHandshake completed24 ms
15 days agoHandshake completed59 ms
15 days agoHandshake completed48 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed38 ms
18 days agoHandshake completed30 ms
20 days agoHandshake completed82 ms
22 days agoHandshake completed102 ms
25 days agoHandshake completed30 ms
27 days agoHandshake completed140 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/standup and makes no claim about it beyond what these checks measured.