# Zovo League Fixtures (remote · league-schedule.zovo.one)

Make a round robin league schedule for 3 to 24 teams on real dates.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `league-schedule.zovo.one`: 78/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule.md), [page](https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule)

## Channel facts

- Endpoint: `https://league-schedule.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-league-schedule 'https://league-schedule.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-league-schedule": {
      "url": "https://league-schedule.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-league-schedule": {
      "type": "http",
      "url": "https://league-schedule.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-league-schedule]
url = "https://league-schedule.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-league-schedule": {
      "type": "remote",
      "url": "https://league-schedule.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-league-schedule --url 'https://league-schedule.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-league-schedule:
    url: "https://league-schedule.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-league-schedule": {
      "Transport": "http",
      "Url": "https://league-schedule.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-league-schedule -t streamable-http -u 'https://league-schedule.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-league-schedule": {
      "type": "http",
      "url": "https://league-schedule.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, +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.

### 2026-11-18 (score 77, +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.

### 2026-11-16 (score 76, +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.

### 2026-11-14 (score 75, +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.

### 2026-11-12 (score 74, +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.

### 2026-11-10 (score 73, +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.

### 2026-11-09 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (1)

### `generate_league_schedule` (~855 tokens)

Generate league schedule

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.

Input parameters:

- `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.

Output parameters:

- `balance` (array)
- `blackouts_skipped` (array)
- `downloads` (object)
- `every_weeks` (number)
- `first_round` (string)
- `format` (string)
- `games_count` (number)
- `last_round` (string)
- `longest_home_or_away_run` (number)
- `notes` (array)
- `play_days` (array)
- `rounds` (array)
- `rounds_count` (number)
- `rounds_shown` (object)
- `teams_count` (number)
- `title` (string)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://league-schedule.zovo.one/mcp
- Website: https://league-schedule.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-league-schedule/league-schedule
