Remote MCP · Endpoint

Zovo Project Timeline MCP server

No. Zovo Project Timeline answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://gantt-timeline.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/gantt-timeline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
240 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A Gantt chart maker and project timeline planner that works inside the chat.
Listing
From the official MCP registry (active).
Recent checks of Zovo Project Timeline
CheckedResultHandshake
56 minutes agoHandshake completed240 ms
3 days agoHandshake completed57 ms
12 days agoHandshake completed473 ms
13 days agoHandshake completed307 ms
14 days agoHandshake completed552 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed258 ms
18 days agoHandshake completed266 ms
18 days agoHandshake completed72 ms
20 days agoHandshake completed419 ms
22 days agoHandshake completed176 ms
25 days agoHandshake completed406 ms
27 days agoHandshake completed209 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 Zovo Project Timeline and makes no claim about it beyond what these checks measured.