Search / io.github.everyai-com/league-night
LeagueNight
R0· no sign-inRound-robin fixtures, standings and match-day plans for league organizers. Free.
v1.0.0 · active · repository · descriptor JSON · versions
Search / io.github.everyai-com/league-night
R0· no sign-inRound-robin fixtures, standings and match-day plans for league organizers. Free.
v1.0.0 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"league-night": {
"type": "http",
"url": "https://league-night.magicteams.ai/mcp"
}
}
}claude mcp add --transport http league-night https://league-night.magicteams.ai/mcp[mcp_servers.league-night]
url = "https://league-night.magicteams.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"league-night": {
"type": "remote",
"url": "https://league-night.magicteams.ai/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"league-night": {
"type": "http",
"url": "https://league-night.magicteams.ai/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=league-night&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbGVhZ3VlLW5pZ2h0Lm1hZ2ljdGVhbXMuYWkvbWNwIn0%3D"
}{
"servers": {
"league-night": {
"type": "http",
"url": "https://league-night.magicteams.ai/mcp"
}
}
}{
"mcpServers": {
"league-night": {
"httpUrl": "https://league-night.magicteams.ai/mcp"
}
}
}extensions:
"league-night":
enabled: true
name: "league-night"
type: streamable_http
uri: "https://league-night.magicteams.ai/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list carries no ttlMs, so clients re-fetch itauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations4 of 4 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 1,406 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes8 tool changes in 30 daysstability.rug_pull8 tools kept their name but changed most of their description in 30 days; review before trusting themdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageseason_planchangeddescription, input schema, output schema, annotationsmeaning changedPlan a season end-to-end. Use when you need a full season overview. Do NOT use when you need to plan a single match day; use match_day_plan instead.
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).
match_day_planchangeddescription, input schema, output schema, annotationsmeaning changedAssign games to courts and time slots for a match day. Use when you need to schedule multiple games across several courts. Do NOT use when you need to generate a full season schedule, use season_plan.
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).
standings_tablechangeddescription, input schema, output schema, annotationsmeaning changedGenerate a standings table from match results. Use when you need to rank teams based on their performance. Do NOT use when you need to plan future matches; use round_robin_schedule instead.
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).
round_robin_schedulechangeddescription, input schema, output schema, annotationsmeaning changedGenerate a round-robin fixture schedule for a set of teams. Use when needing a balanced, circular schedule. Avoid when needing a single matchday plan (use match_day_plan).
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).
season_planchangedtitle, description, output schema, annotationsmeaning changedSize a season end-to-end: total fixtures from the round-robin, games per match day given the courts available, match days needed, and the calendar dates from a start date to the estimated finish date.
Plan a season end-to-end. Use when you need a full season overview. Do NOT use when you need to plan a single match day; use match_day_plan instead.
match_day_planchangedtitle, description, output schema, annotationsmeaning changedLay an ordered list of games onto a courts-by-slots time grid: game i goes to court (i mod courts) in slot (i div courts) and each slot is slot_minutes long, starting at start_time.
Assign games to courts and time slots for a match day. Use when you need to schedule multiple games across several courts. Do NOT use when you need to generate a full season schedule, use season_plan.
standings_tablechangedtitle, description, output schema, annotationsmeaning changedAggregate match results into a league table with played, wins, draws, losses, goals for/against, goal difference and points, sorted by points, then goal difference, then goals for, then name.
Generate a standings table from match results. Use when you need to rank teams based on their performance. Do NOT use when you need to plan future matches; use round_robin_schedule instead.
round_robin_schedulechangedtitle, description, output schema, annotationsmeaning changedBuild a circle-method round-robin fixture schedule: every pair of teams meets once, or twice when second_leg is set. Odd team counts get one bye per round.
Generate a round-robin fixture schedule for a set of teams. Use when needing a balanced, circular schedule. Avoid when needing a single matchday plan (use match_day_plan).
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +reachable +uptime-98% +updated-16d-ago -duplicate-repo(15 names)
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://league-night.magicteams.ai/mcp streamable-http | none | yes | 98% | 257 ms | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 | 2026-10-20 |
match_day_planread-only | 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). |
round_robin_scheduleread-only | 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). |
season_planread-only | 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). |
standings_tableread-only | 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). |
Schemas: list_tools.
14 other active names share this repository (showing 10): io.github.everyai-com/ai-ready, io.github.everyai-com/court-split, io.github.everyai-com/fee-fighter, io.github.everyai-com/festival-finder, io.github.everyai-com/flight-fix, io.github.everyai-com/invoice-gen, io.github.everyai-com/lease-break, io.github.everyai-com/party-plan, io.github.everyai-com/recipe-scale, io.github.everyai-com/report-raja
And 9 more from this publisher.
{
"name": "io.github.everyai-com/league-night",
"title": "LeagueNight",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://league-night.magicteams.ai/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/everyai-com/sahadeva",
"source": "github"
},
"description": "Round-robin fixtures, standings and match-day plans for league organizers. Free."
}