Zovo League Fixtures
REMOTE · LEAGUE-SCHEDULE.ZOVO.ONE
Make a round robin league schedule for 3 to 24 teams on real dates.
Available components
Last scanned (22 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Project Management
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability66
- 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 989 tokens (~494/item across 2 items; 1 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 Management43
- Stability observed for 13 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 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 21 Nov 2026 · Probed https://league-schedule.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 | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1a6be51dae225a780e14b5b59cd24fa3 |
| SANs: zovo.one, *.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 league-schedule.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| one. | DS published | 64939 | 8 | Verified |
| zovo.one. | No DS | 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://league-schedule.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://league-schedule.zovo.one/mcp | HTTPS enforced | 301 | https://league-schedule.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 →
generate_league_schedule Generate league schedule ~855
Use this when the user wants a league schedule, round robin schedule, fixture list, season schedule or a home and away schedule for 3 to 24 teams ("make a schedule for my 8-team rec league", "round robin for 6 teams on Saturdays", "each team plays each other twice"). Put the team names into teams (convert a pasted list), plus start_date, play_days, format (single or double; use single when the user does not say), and optional blackout_dates, venues, time_slots or kickoff_time. When the user gives only a number of teams, call with placeholder names such as Team 1, Team 2. Each pair meets once (or twice, home and away); no team plays twice in a round; byes are even for an odd number of teams; home and away games are balanced. Returns the rounds on real dates, a printable PDF, an Excel workbook, an ICS with all games and one ICS per team. Refuses when the rounds do not fit before end_date or the venue slots are too few, and says what to change. Does not record scores or standings and does not make knockout brackets.
| Name | Type | Req | Description |
|---|---|---|---|
| blackout_dates | – | – | Dates with no games (holidays, school breaks): ["2027-02-13", "2027-04-03 to 2027-04-10"] or [{"from":"2026-12-20","to":"2027-01-03","reason":"Winter break"}]. Rounds move to the next play date. |
| date_order | string|null | – | Optional order for dates like 03/04/2027: "mdy" (US, default) or "dmy". |
| end_date | string|null | – | Optional last allowed date, e.g. "2027-05-31". If the rounds do not fit, the tool says how many dates are missing and what to change. |
| every_weeks | number|string|null | – | 1 (default) for every week, 2 for every other week, up to 4. |
| format | string|null | – | "single" (default): every pair plays once. "double": every pair plays twice, home and away (the second half repeats the pairings with home and away swapped). |
| game_minutes | number|string|null | – | Length of a game in the calendar files, 10 to 600 minutes. Default 90. |
| kickoff_time | string|null | – | Optional single kickoff time for every game, e.g. "19:00" or "7pm". Ignored when time_slots is given. |
| page_size | string|null | – | "Letter" (default) or "A4". |
| play_days | – | – | Weekday(s) with games, e.g. ["Saturday"] or ["Tuesday","Thursday"] (one round on each play date). Default: the weekday of start_date. |
| start_date | string|null | – | Date of the first round, e.g. "2027-01-09". Required. |
| teams | – | – | The teams, 3 to 24: ["Lions","Tigers","Bears","Wolves"] or objects with a home venue [{"name":"Lions","venue":"Riverside Park"}]. Names must be different. Convert a pasted list into this array. |
| teams_text | string|null | – | Fallback only: team names pasted as text, one per line or comma separated. Prefer teams. |
| time_slots | – | – | Optional kickoff times on a play date, e.g. ["09:00","10:30","12:00"]. Slots rotate between rounds so no team always plays first. |
| timezone | string|null | – | Optional IANA time zone for the calendar files, e.g. "America/Chicago". Without it, times are local clock times. |
| title | string|null | – | Optional league name printed on the schedule, e.g. "Spring U10 League". |
| venues | – | – | Optional shared venues used by all teams, e.g. ["Field 1","Field 2"]. With time_slots, each round fills venue x time slots. Leave empty to use each team's home venue. |
| Name | Type | Req | Description |
|---|---|---|---|
| balance | array | yes | – |
| blackouts_skipped | array | yes | – |
| downloads | object | yes | – |
| every_weeks | number | yes | – |
| first_round | string | yes | – |
| format | string | yes | – |
| games_count | number | yes | – |
| last_round | string | yes | – |
| longest_home_or_away_run | number | yes | – |
| notes | array | yes | – |
| play_days | array | yes | – |
| rounds | array | yes | – |
| rounds_count | number | yes | – |
| rounds_shown | object | – | – |
| teams_count | number | yes | – |
| title | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Zovo League Fixtures MCP server?
Zovo League Fixtures is a hosted endpoint at https://league-schedule.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 · league-schedule.zovo.one
claude mcp add --transport http theluckystrike-league-schedule 'https://league-schedule.zovo.one/mcp'
What is the Zovo League Fixtures MCP server?
Zovo League Fixtures is an MCP server listed in the public MCP registry as io.github.theluckystrike/league-schedule. Make a round robin league schedule for 3 to 24 teams on real dates. This page covers its hosted endpoint (https://league-schedule.zovo.one/mcp).
Is the Zovo League Fixtures MCP server safe to use?
Zovo League Fixtures scores 78 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 League Fixtures MCP server expose?
Zovo League Fixtures exposes 1 tool: generate_league_schedule. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.
Does the Zovo League Fixtures MCP server require authentication?
No. We connected to Zovo League Fixtures without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo League Fixtures MCP server still maintained?
Zovo League Fixtures is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Zovo League Fixtures MCP server?
VerifyMCP ran 14 checks on Zovo League Fixtures, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.