accueil / serveurs / Dev & Code / io.github.everyai-com/court-split
io.github.everyai-com/court-split
serveur MCP (Model Context Protocol) · court-split 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/court-split est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.everyai-com/court-split » 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
- rotation_plan≈ 621 tokens
Plan fair player rotations for pickup games: who plays on each court every round and who sits out, balancing games played across the roster. Use when more players show up than court spots. Does not split money; for costs use split_costs or split_series.
Paramètres, retour & exemple (4)
Paramètrescourts· integer · optionnel
Number of courts in use at once (default 1)rounds· integer · requis
Number of rounds to schedule, 1-50players· array · requis
Unique roster names, at least capacity x courts of them, e.g. ["Asha","Dev","Mira","Sam","Lee","Kai"]capacity· integer · requis
Players per court: 2 for singles, 4 for doubles, 10 for 5v5 basketball
Exemple d'appel{"name": "rotation_plan", "arguments": {"rounds": 1, "players": [], "capacity": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "format": "texte", "rounds": 1, "fairness": {}, "schedule": []}} - settle_up≈ 732 tokens
Given a shared total and who already paid what, compute each player's balance and the minimal set of payments (who pays whom, how much) to settle everyone. Use when the question is 'who owes whom'. For recurring sessions with different attendees use split_series.
Paramètres, retour & exemple (4)
Paramètresshares· array · optionnel
Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal splitcurrency· string · optionnel
Currency code used only for display, e.g. USD, EUR, GBP (default USD)total_cost· number · requis
Total court/venue cost in currency units, e.g. 96 for $96.00participants· array · requis
At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{"name":"Asha","paid":96},{"name":"Dev"}]
Exemple d'appel{"name": "settle_up", "arguments": {"total_cost": 1, "participants": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "balances": [], "currency": "texte", "transfers": [], "total_cost": 1, "transfer_count": 1}} - split_costs≈ 779 tokens
Split one total court or venue cost across players, equally or by relative weights, and show each player's share plus the fewest payments to settle up. Use for a single booking or event. For recurring sessions with changing attendance use split_series.
Paramètres, retour & exemple (4)
Paramètresshares· array · optionnel
Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal splitcurrency· string · optionnel
Currency code used only for display, e.g. USD, EUR, GBP (default USD)total_cost· number · requis
Total court/venue cost in currency units, e.g. 96 for $96.00participants· array · requis
At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{"name":"Asha","paid":96},{"name":"Dev"}]
Exemple d'appel{"name": "split_costs", "arguments": {"total_cost": 1, "participants": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "split": "equal", "currency": "texte", "per_head": 1, "settle_up": [], "total_cost": 1, "participants": []}} - split_series≈ 957 tokens
Split a series of recurring sessions where attendance varies: each session's cost is shared only by that session's attendees, then payments already made are netted into balances and minimal settle-up transfers. Use for weekly games or leagues. For a single event use split_costs.
Paramètres, retour & exemple (4)
Paramètresplayers· array · optionnel
Optional full roster, so players who missed every session still appear with a zero balancecurrency· string · optionnel
Currency code used only for display, e.g. USD (default USD)payments· array · optionnel
Optional list of who already paid what across the series, e.g. [{"name":"Asha","paid":120}]sessions· array · requis
Sessions in order, each with its cost and the names who attended
Exemple d'appel{"name": "split_series", "arguments": {"sessions": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "players": [], "currency": "texte", "sessions": [], "transfers": [], "total_cost": 1, "session_count": 1}}
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é ».