LeagueNight
REMOTE · LEAGUE-NIGHT.MAGICTEAMS.AI
Round-robin fixtures, standings and match-day plans for league organizers. Free.
Available components
Last scanned (14 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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 896 tokens (~224/item across 4 items; 4 tools + 0 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 Management23
- Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 16 to 19.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 9 to 13.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 6.
- 10 Oct 26 −2
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “match_day_plan” rewrote its description, which is the text the model reads security
- Tool “round_robin_schedule” rewrote its description, which is the text the model reads security
- Tool “season_plan” rewrote its description, which is the text the model reads security
- Tool “standings_table” rewrote its description, which is the text the model reads security
- Schema quality: 127 → 224 ▼ functional
- “match_day_plan” changed the type of “courts”: number → integer ▼ functional
- “match_day_plan” changed the type of “slot_minutes”: number → integer ▼ functional
- “round_robin_schedule” changed the type of “rounds”: number → integer ▼ functional
- “season_plan” changed the type of “courts”: number → integer ▼ functional
- “season_plan” changed the type of “days_between_rounds”: number → integer ▼ functional
- “season_plan” changed the type of “slot_minutes”: number → integer ▼ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “match_day_plan” reworded the description of “courts” cosmetic
- “match_day_plan” reworded the description of “games” cosmetic
- “match_day_plan” reworded the description of “slot_minutes” cosmetic
- “match_day_plan” reworded the description of “start_time” cosmetic
- “round_robin_schedule” reworded the description of “rounds” cosmetic
- “round_robin_schedule” reworded the description of “second_leg” cosmetic
- “round_robin_schedule” reworded the description of “teams” cosmetic
- “season_plan” reworded the description of “courts” cosmetic
- “season_plan” reworded the description of “days_between_rounds” cosmetic
- “season_plan” reworded the description of “second_leg” cosmetic
- “season_plan” reworded the description of “slot_minutes” cosmetic
- “season_plan” reworded the description of “start_date” cosmetic
- “season_plan” reworded the description of “teams” cosmetic
- “standings_table” reworded the description of “points_draw” cosmetic
- “standings_table” reworded the description of “points_win” cosmetic
- “standings_table” reworded the description of “results” cosmetic
- “standings_table” reworded the description of “teams” cosmetic
- 6 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 4 Oct 26 71
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://league-night.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | efec6bce4d2fe5d40e68198214be575c |
| SANs: magicteams.ai, league-night.magicteams.ai, *.league-night.magicteams.ai | ||||||
| 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-night.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://league-night.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://league-night.magicteams.ai/mcp | HTTPS enforced | 301 | https://league-night.magicteams.ai/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 →
match_day_plan Match day plan ~204
Compute a one-day timetable: lay an ordered list of games onto parallel courts and fixed-length time slots from a start time, giving each game a court and HH:MM start, plus the end time. Use when you already know the day's games. Do NOT use to decide who plays whom (use round_robin_schedule) or to size a whole season (use season_plan).
| Name | Type | Req | Description |
|---|---|---|---|
| courts | integer | yes | Number of courts/pitches usable at the same time, integer 1-12, e.g. 2 |
| games | array | yes | Games in the order they should be played (non-empty); e.g. one round's fixtures from round_robin_schedule |
| slot_minutes | integer | yes | Length of one game slot in minutes, integer 10-180, e.g. 40 |
| start_time | string | yes | First game start, 24h HH:MM, e.g. "09:00" or "18:30" |
| Name | Type | Req | Description |
|---|---|---|---|
| courts | integer | yes | Number of courts used in parallel |
| end_time | string | yes | Time the last slot finishes, 24h HH:MM (wraps past midnight) |
| note | string | yes | Plain-English summary (slots, courts, after-midnight warning) |
| slot_minutes | integer | yes | Length of each slot in minutes |
| start_time | string | yes | First slot start time, 24h HH:MM (echoed from input) |
| timeline | array | yes | One entry per game, in input order |
| total_minutes | integer | yes | Total duration from first start to last finish, in minutes |
No examples provided.
round_robin_schedule Round robin schedule ~203
Compute a round-robin fixture list (circle method) for 2-100 teams: every pair meets once, or twice home-and-away with second_leg; odd counts get one bye per round. Use when you need who plays whom in each round. Do NOT use to assign times/courts for one match day (use match_day_plan) or to get calendar dates for a season (use season_plan).
| Name | Type | Req | Description |
|---|---|---|---|
| rounds | integer | – | Optional: return only the first N rounds, integer 1..max (max = teams-1 for even counts, teams for odd; doubled with second_leg). Default: all rounds |
| second_leg | boolean | – | If true, append a mirrored second leg with home and away swapped (double round-robin). Default false |
| teams | array | yes | Team names: 2-100 unique, non-empty names (trimmed), e.g. ["Falcons", "Tigers", "Bears"] |
| Name | Type | Req | Description |
|---|---|---|---|
| games_per_team | number | yes | Average games per team across the returned rounds (2 decimals) |
| legs | integer | yes | Number of legs included in the returned rounds (1 or 2) |
| note | string | yes | Plain-English summary of the schedule (teams, rounds, byes, truncation) |
| rounds | array | yes | Rounds in play order, each with its fixtures and any bye |
| teams | array | yes | Cleaned (trimmed) team names in input order |
| total_games | integer | yes | Total fixtures (excluding byes) in the returned rounds |
No examples provided.
season_plan Season plan ~280
Estimate a season's size and calendar: total round-robin fixtures, games per match day (limited by courts, one slot per day), match days needed, every match-day date from start_date at a fixed interval, and the finish date. Use for "when will the season end?". Do NOT use for pairings (use round_robin_schedule) or one day's timetable (use match_day_plan).
| Name | Type | Req | Description |
|---|---|---|---|
| courts | integer | yes | Courts usable at the same time on each match day, integer 1-12; caps games per match day. E.g. 2 |
| days_between_rounds | integer | – | Days between consecutive match days, integer 1-60. Default 7 (weekly) |
| second_leg | boolean | – | If true, plan a double round-robin (each pair meets twice). Default false |
| slot_minutes | integer | yes | Length of one game slot in minutes, integer 10-180 (validated and echoed in the note; each match day is one slot). E.g. 30 |
| start_date | string | yes | First match day, YYYY-MM-DD, e.g. "2026-10-04" |
| teams | array | yes | Team names: 2-100 unique, non-empty names (trimmed), e.g. ["Falcons", "Tigers", "Bears"] |
| Name | Type | Req | Description |
|---|---|---|---|
| dates | array | yes | Every match-day date, YYYY-MM-DD, in order |
| finish_date | string | yes | Date of the last match day, YYYY-MM-DD |
| games_per_round | integer | yes | Games played per match day: min(floor(teams/2), courts) |
| games_total | integer | yes | Total fixtures in the season (n(n-1)/2 per leg) |
| note | string | yes | Plain-English summary of the season plan and assumptions |
| per_team_games | integer | yes | Games each team plays over the season |
| rounds_needed | integer | yes | Number of match days needed to play all fixtures |
No examples provided.
standings_table Standings table ~174
Compute a league standings table from match results: played, W/D/L, goals for/against, goal difference and points, sorted by points, then goal difference, then goals for, then name. Use when you have scores and want the current table. Do NOT use to generate future fixtures (use round_robin_schedule).
| Name | Type | Req | Description |
|---|---|---|---|
| points_draw | number | – | Points awarded for a draw, non-negative number. Default 1 |
| points_win | number | – | Points awarded for a win, non-negative number. Default 3 |
| results | array | yes | Completed match results in any order; may be empty if teams is given (zeroed table) |
| teams | array | – | Optional full roster (2+ unique names). Teams with no results appear with zeros; results involving teams not listed are skipped with a warning |
| Name | Type | Req | Description |
|---|---|---|---|
| points_system | object | yes | Points scheme applied to compute the table |
| table | array | yes | Standings rows sorted by points, goal difference, goals for, then team name |
| warnings | array | yes | Results skipped because a team was not in the roster (empty if none) |
No examples provided.
How do I install the LeagueNight MCP server?
LeagueNight is a hosted endpoint at https://league-night.magicteams.ai/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-night.magicteams.ai
claude mcp add --transport http everyai-com-league-night 'https://league-night.magicteams.ai/mcp'
What is the LeagueNight MCP server?
LeagueNight is an MCP server listed in the public MCP registry as io.github.everyai-com/league-night. Round-robin fixtures, standings and match-day plans for league organizers. Free. This page covers its hosted endpoint (https://league-night.magicteams.ai/mcp).
Is the LeagueNight MCP server safe to use?
LeagueNight 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 LeagueNight MCP server expose?
LeagueNight exposes 4 tools: round_robin_schedule, standings_table, match_day_plan, season_plan. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.
Does the LeagueNight MCP server require authentication?
No. We connected to LeagueNight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LeagueNight MCP server still maintained?
LeagueNight 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.