accueil / serveurs / Productivité / io.github.everyai-com/league-night
io.github.everyai-com/league-night
serveur MCP (Model Context Protocol) · league-night 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.everyai-com/league-night est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.everyai-com/league-night » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 4 outils
- match_day_plan≈ 680 tokens
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).
Paramètres, retour & exemple (4)
Paramètresgames· array · requis
Games in the order they should be played (non-empty); e.g. one round's fixtures from round_robin_schedulecourts· integer · requis
Number of courts/pitches usable at the same time, integer 1-12, e.g. 2start_time· string · requis
First game start, 24h HH:MM, e.g. "09:00" or "18:30"slot_minutes· integer · requis
Length of one game slot in minutes, integer 10-180, e.g. 40
Exemple d'appel{"name": "match_day_plan", "arguments": {"games": [], "courts": 1, "start_time": "texte", "slot_minutes": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "courts": 1, "end_time": "texte", "timeline": [], "start_time": "texte", "slot_minutes": 1, "total_minutes": 1}} - round_robin_schedule≈ 662 tokens
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).
Paramètres, retour & exemple (3)
Paramètresteams· array · requis
Team names: 2-100 unique, non-empty names (trimmed), e.g. ["Falcons", "Tigers", "Bears"]rounds· integer · optionnel
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 roundssecond_leg· boolean · optionnel
If true, append a mirrored second leg with home and away swapped (double round-robin). Default false
Exemple d'appel{"name": "round_robin_schedule", "arguments": {"teams": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"legs": 1, "note": "texte", "teams": [], "rounds": [], "total_games": 1, "games_per_team": 1}} - season_plan≈ 668 tokens
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).
Paramètres, retour & exemple (6)
Paramètresteams· array · requis
Team names: 2-100 unique, non-empty names (trimmed), e.g. ["Falcons", "Tigers", "Bears"]courts· integer · requis
Courts usable at the same time on each match day, integer 1-12; caps games per match day. E.g. 2second_leg· boolean · optionnel
If true, plan a double round-robin (each pair meets twice). Default falsestart_date· string · requis
First match day, YYYY-MM-DD, e.g. "2026-10-04"slot_minutes· integer · requis
Length of one game slot in minutes, integer 10-180 (validated and echoed in the note; each match day is one slot). E.g. 30days_between_rounds· integer · optionnel
Days between consecutive match days, integer 1-60. Default 7 (weekly)
Exemple d'appel{"name": "season_plan", "arguments": {"teams": [], "courts": 1, "start_date": "texte", "slot_minutes": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "dates": [], "finish_date": "texte", "games_total": 1, "rounds_needed": 1, "per_team_games": 1, "games_per_round": 1}} - standings_table≈ 772 tokens
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).
Paramètres, retour & exemple (4)
Paramètresteams· array · optionnel
Optional full roster (2+ unique names). Teams with no results appear with zeros; results involving teams not listed are skipped with a warningresults· array · requis
Completed match results in any order; may be empty if teams is given (zeroed table)points_win· number · optionnel
Points awarded for a win, non-negative number. Default 3points_draw· number · optionnel
Points awarded for a draw, non-negative number. Default 1
Exemple d'appel{"name": "standings_table", "arguments": {"results": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"table": [], "warnings": [], "points_system": {}}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».