MCP.Market

Zovo Tournament Maker MCP server

online · 100% uptime
by theluckystrike·io.github.theluckystrike/bracket-maker·v1.0.0

Make a tournament bracket in the chat, record results by clicking the winners, and print it.

C67/100grade C
What users say
No reviews yet
Be the first
Safety scan
C67/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Zovo Tournament Maker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Zovo Tournament Maker tools (2)

write = sends, deletes, buys or posts
  • calculate_bracket_standingsFree

    Use this when the user reports results of a tournament made with generate_tournament_bracket (or describes one) and wants the updated bracket, who advances, the standings table or what is next. Takes the same format and participants plus every result so far (winner or scores per match) and returns the advanced bracket, the round robin or Swiss table (points, head-to-head, score difference; Buchholz for Swiss), final places, the next Swiss round's pairings, and the next matches to play. Do not use to predict outcomes; it only records results the user gives.

  • generate_tournament_bracketFree

    Use this when the user wants a tournament bracket or schedule (tournament bracket maker, bracket generator, single elimination or double elimination bracket, round robin schedule generator, Swiss pairings, a bracket for 6, 10 or 12 teams with byes). Builds the full structure for 2-128 players or teams: standard seeding so top seeds meet last, byes for the top seeds when the field is not a power of two, optional third-place match, grand final reset, round robin via the circle method with balanced home/away, Swiss round 1, optional timetable over several courts, a printable PDF bracket and a CSV schedule. Results already known can be included to advance winners. Does not predict winners, fill in picks for famous tournaments, or schedule leagues with venue or travel constraints.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1014ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Zovo Tournament Maker compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
67/100
higher than 25% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
304 ms
faster than 47% of 30,031 servers

What its tools let an agent do: 1 read · 1 create

Install Zovo Tournament Maker in Claude Code, Cursor or VS Code

claude mcp add --transport http bracket-maker https://bracket-maker.zovo.one/mcp
Add to Cursor

Zovo Tournament Maker: common questions

Is Zovo Tournament Maker MCP server safe?
With care: it is graded C, so read the findings first (67/100). Read the Zovo Tournament Maker safety report
How do I install Zovo Tournament Maker?
It runs remotely at bracket-maker.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Zovo Tournament Maker need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Zovo Tournament Maker maintained?
The latest release is v1.0.0.
Is Zovo Tournament Maker up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Zovo Tournament Maker compare with other MCP servers?
safety score 67/100 (higher than 25% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.