Remote MCP · Endpoint

Zovo Tournament Maker MCP server

No. Zovo Tournament Maker answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://bracket-maker.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/bracket-maker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
325 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Make a tournament bracket in the chat, record results by clicking the winners, and print it.
Listing
From the official MCP registry (active).
Recent checks of Zovo Tournament Maker
CheckedResultHandshake
56 minutes agoHandshake completed325 ms
3 days agoHandshake completed267 ms
12 days agoHandshake completed508 ms
13 days agoHandshake completed525 ms
14 days agoHandshake completed694 ms
15 days agoHandshake completed328 ms
17 days agoHandshake completed661 ms
18 days agoHandshake completed339 ms
18 days agoHandshake completed266 ms
20 days agoHandshake completed392 ms
22 days agoHandshake completed298 ms
25 days agoHandshake completed348 ms
27 days agoHandshake completed277 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 Tournament Maker and makes no claim about it beyond what these checks measured.