Zovo Tournament Maker
REMOTE · BRACKET-MAKER.ZOVO.ONE
Make a tournament bracket in the chat, record results by clicking the winners, and print it.
Available components
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1968 tokens (~656/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://bracket-maker.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 96cbcba13aa688d0133083d555946927 |
| SANs: zovo.one, bracket-maker.zovo.one, *.bracket-maker.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bracket-maker.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bracket-maker.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://bracket-maker.zovo.one/mcp | HTTPS enforced | 301 | https://bracket-maker.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_bracket_standings Calculate bracket standings ~902
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.
| Name | Type | Req | Description |
|---|---|---|---|
| break_minutes | number | – | Changeover time between matches on a court, in minutes (0-120, default 0). Example: 5 |
| courts | number | – | Courts, tables, boards or fields available at the same time (1-64), used for the timetable. Example: 3 |
| draw_points | number | – | Points for a draw (default 1 for round robin, 0.5 for Swiss). Example: 1 |
| format | string | yes | Tournament format: single_elimination (knockout), double_elimination (out after two losses, losers bracket, grand final), round_robin (everyone plays everyone once; league), swiss (fixed number of ro… |
| grand_final_reset | boolean | – | Double elimination only (default true): if the losers-bracket champion wins the grand final, a second deciding match is played, so nobody is out after one loss. Example: false |
| loss_points | number | – | Points for a loss (default 0). Example: 0 |
| match_minutes | number | – | Length of one match in minutes (5-600). Giving this adds start times and courts to every match. Example: 20 |
| meetings | number | – | Round robin only: 1 (default) = every pair meets once; 2 = home and away (double round robin). Example: 2 |
| paper | string | – | Paper size for the landscape PDF: letter (default) or a4. Example: a4 |
| participant_count | number | – | Use instead of participants when the user gives only a number: makes Team 1 ... Team N (2-128). Example: 12 |
| participants | array | – | Players or teams, 2-128 unique names. With standard seeding the order is the ranking: first = seed 1. Example: ["Ann","Bob","Cy","Dee","Eve","Finn"] |
| random_seed | number | – | Draw number for random seeding (1-999999). The same participants and number always give the same draw. Example: 4821 |
| results | array | – | Results already played, in any order for elimination formats and round by round for Swiss. Each needs the players (p1, p2) or a match id, plus a winner or both scores. Example: [{"p1":"Ann","p2":"Fin… |
| seeding | string | – | standard (default): list order is the seed ranking, 1 plays the lowest seed, top seeds get the byes and seeds 1 and 2 can only meet in the final. random: a reproducible random draw (see random_seed),… |
| start_time | string | – | Start time of the first matches, 24-hour HH:MM (default 09:00). Example: "18:30" |
| swiss_rounds | number | – | Swiss only: number of rounds (default log2 of the field, rounded up; maximum depends on the field size). Example: 5 |
| third_place_match | boolean | – | Single elimination only: add a third-place match between the semifinal losers. Example: true |
| title | string | – | Tournament name for the bracket, PDF and CSV. Example: "Friday Ping Pong Cup" |
| win_points | number | – | Round robin / Swiss table points for a win (default 3 for round robin, 1 for Swiss). Example: 2 |
| Name | Type | Req | Description |
|---|---|---|---|
| bracket_size | number|null | yes | – |
| byes | array | yes | – |
| champion | string|null | yes | – |
| complete | boolean | yes | – |
| counts | object | yes | – |
| downloads | object | yes | – |
| format | string | yes | – |
| format_label | string | yes | – |
| kind | string | yes | – |
| matches | array | yes | – |
| next_matches | array | yes | – |
| notes | array | yes | – |
| participants | array | yes | – |
| placements | array | yes | – |
| random_seed | number|null | yes | – |
| request | object | yes | – |
| results | array | yes | – |
| schedule | – | yes | – |
| seeding | string | yes | – |
| standings | array | yes | – |
| swiss | – | yes | – |
| title | string | yes | – |
No examples provided.
generate_tournament_bracket Generate tournament bracket ~946
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.
| Name | Type | Req | Description |
|---|---|---|---|
| break_minutes | number | – | Changeover time between matches on a court, in minutes (0-120, default 0). Example: 5 |
| courts | number | – | Courts, tables, boards or fields available at the same time (1-64), used for the timetable. Example: 3 |
| draw_points | number | – | Points for a draw (default 1 for round robin, 0.5 for Swiss). Example: 1 |
| format | string | yes | Tournament format: single_elimination (knockout), double_elimination (out after two losses, losers bracket, grand final), round_robin (everyone plays everyone once; league), swiss (fixed number of ro… |
| grand_final_reset | boolean | – | Double elimination only (default true): if the losers-bracket champion wins the grand final, a second deciding match is played, so nobody is out after one loss. Example: false |
| loss_points | number | – | Points for a loss (default 0). Example: 0 |
| match_minutes | number | – | Length of one match in minutes (5-600). Giving this adds start times and courts to every match. Example: 20 |
| meetings | number | – | Round robin only: 1 (default) = every pair meets once; 2 = home and away (double round robin). Example: 2 |
| paper | string | – | Paper size for the landscape PDF: letter (default) or a4. Example: a4 |
| participant_count | number | – | Use instead of participants when the user gives only a number: makes Team 1 ... Team N (2-128). Example: 12 |
| participants | array | – | Players or teams, 2-128 unique names. With standard seeding the order is the ranking: first = seed 1. Example: ["Ann","Bob","Cy","Dee","Eve","Finn"] |
| random_seed | number | – | Draw number for random seeding (1-999999). The same participants and number always give the same draw. Example: 4821 |
| results | array | – | Results already played, in any order for elimination formats and round by round for Swiss. Each needs the players (p1, p2) or a match id, plus a winner or both scores. Example: [{"p1":"Ann","p2":"Fin… |
| seeding | string | – | standard (default): list order is the seed ranking, 1 plays the lowest seed, top seeds get the byes and seeds 1 and 2 can only meet in the final. random: a reproducible random draw (see random_seed),… |
| start_time | string | – | Start time of the first matches, 24-hour HH:MM (default 09:00). Example: "18:30" |
| swiss_rounds | number | – | Swiss only: number of rounds (default log2 of the field, rounded up; maximum depends on the field size). Example: 5 |
| third_place_match | boolean | – | Single elimination only: add a third-place match between the semifinal losers. Example: true |
| title | string | – | Tournament name for the bracket, PDF and CSV. Example: "Friday Ping Pong Cup" |
| win_points | number | – | Round robin / Swiss table points for a win (default 3 for round robin, 1 for Swiss). Example: 2 |
| Name | Type | Req | Description |
|---|---|---|---|
| bracket_size | number|null | yes | – |
| byes | array | yes | – |
| champion | string|null | yes | – |
| complete | boolean | yes | – |
| counts | object | yes | – |
| downloads | object | yes | – |
| format | string | yes | – |
| format_label | string | yes | – |
| kind | string | yes | – |
| matches | array | yes | – |
| next_matches | array | yes | – |
| notes | array | yes | – |
| participants | array | yes | – |
| placements | array | yes | – |
| random_seed | number|null | yes | – |
| request | object | yes | – |
| results | array | yes | – |
| schedule | – | yes | – |
| seeding | string | yes | – |
| standings | array | yes | – |
| swiss | – | yes | – |
| title | string | yes | – |
No examples provided.
How do I install the Zovo Tournament Maker MCP server?
Zovo Tournament Maker is a hosted endpoint at https://bracket-maker.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bracket-maker.zovo.one
claude mcp add --transport http theluckystrike-bracket-maker 'https://bracket-maker.zovo.one/mcp'
What is the Zovo Tournament Maker MCP server?
Zovo Tournament Maker is an MCP server listed in the public MCP registry as io.github.theluckystrike/bracket-maker. Make a tournament bracket in the chat, record results by clicking the winners, and print it. This page covers its hosted endpoint (https://bracket-maker.zovo.one/mcp).
Is the Zovo Tournament Maker MCP server safe to use?
Zovo Tournament Maker scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zovo Tournament Maker MCP server expose?
Zovo Tournament Maker exposes 2 tools: generate_tournament_bracket, calculate_bracket_standings. Their descriptions and schemas cost roughly 1,848 tokens of context every time the server is loaded.
Does the Zovo Tournament Maker MCP server require authentication?
No. We connected to Zovo Tournament Maker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Tournament Maker MCP server still maintained?
Zovo Tournament Maker is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.