# CourtSplit (remote · court-split.magicteams.ai)

Split court costs, settle up and plan fair rotations for pickup games. Free.

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

## Components

- remote · `court-split.magicteams.ai`: 77/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-court-split/court-split.md), [page](https://verifymcp.io/servers/everyai-com-court-split/court-split)

## Channel facts

- Endpoint: `https://court-split.magicteams.ai/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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 731 tokens (~182/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 48/100
  - Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the CourtSplit MCP server?

CourtSplit is a hosted endpoint at https://court-split.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.

### Claude

```bash
claude mcp add --transport http everyai-com-court-split 'https://court-split.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-court-split": {
      "url": "https://court-split.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everyai-com-court-split": {
      "type": "http",
      "url": "https://court-split.magicteams.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everyai-com-court-split]
url = "https://court-split.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-court-split": {
      "type": "remote",
      "url": "https://court-split.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-court-split --url 'https://court-split.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-court-split:
    url: "https://court-split.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-court-split": {
      "Transport": "http",
      "Url": "https://court-split.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-court-split -t streamable-http -u 'https://court-split.magicteams.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everyai-com-court-split": {
      "type": "http",
      "url": "https://court-split.magicteams.ai/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-10-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 44 to 48.

### 2026-10-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

### 2026-10-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.

### 2026-10-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.

### 2026-10-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.

### 2026-10-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 4 to 11.

### 2026-10-10 (score 71, −2)

- [security regression] Stability: 0.17 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security] Tool “rotation_plan” rewrote its description, which is the text the model reads
- [security] Tool “settle_up” rewrote its description, which is the text the model reads
- [security] Tool “split_costs” rewrote its description, which is the text the model reads
- [security] Tool “split_series” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional regression] “rotation_plan” changed the type of “capacity”: number → integer
- [functional regression] “rotation_plan” changed the type of “courts”: number → integer
- [functional regression] “rotation_plan” changed the type of “rounds”: number → integer
- [functional] Schema quality: good → excellent
- [cosmetic] “rotation_plan” reworded the description of “capacity”
- [cosmetic] “rotation_plan” reworded the description of “courts”
- [cosmetic] “rotation_plan” reworded the description of “players”
- [cosmetic] “rotation_plan” reworded the description of “rounds”
- [cosmetic] “settle_up” reworded the description of “currency”
- [cosmetic] “settle_up” reworded the description of “participants”
- [cosmetic] “settle_up” reworded the description of “shares”
- [cosmetic] “settle_up” reworded the description of “total_cost”
- [cosmetic] “split_costs” reworded the description of “currency”
- [cosmetic] “split_costs” reworded the description of “participants”
- [cosmetic] “split_costs” reworded the description of “shares”
- [cosmetic] “split_costs” reworded the description of “total_cost”
- [cosmetic] “split_series” reworded the description of “currency”
- [cosmetic] “split_series” reworded the description of “payments”
- [cosmetic] “split_series” reworded the description of “players”
- [cosmetic] “split_series” reworded the description of “sessions”

### 2026-10-09 (score 73, +5)

- [functional regression] Schema quality: 80 → 117
- [functional improvement] Tool coverage: 38% → 100%
- [functional improvement] Stability: unverified → 0.17
- [functional] First check of Tool coverage: 100

## MCP tools (4)

### `split_costs` (~187 tokens)

Split costs

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.

Input parameters:

- `currency` (string): Currency code used only for display, e.g. USD, EUR, GBP (default USD)
- `participants` (array, required): At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{"name":"Asha","paid":96},{"name":"Dev"}]
- `shares` (array): Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal split
- `total_cost` (number, required): Total court/venue cost in currency units, e.g. 96 for $96.00

Output parameters:

- `currency` (string): Currency code used for display
- `note` (string): Plain-language summary of the split
- `participants` (array): Per-player paid, owed share and balance
- `per_head` (number|null): Equal share per player, or null for a weighted split
- `settle_up` (array): Fewest payments that settle everyone (empty if nobody paid yet or all square)
- `split` (string): Whether the split was equal or by relative weights
- `total_cost` (number): Total cost that was split, rounded to cents

### `settle_up` (~190 tokens)

Settle up

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.

Input parameters:

- `currency` (string): Currency code used only for display, e.g. USD, EUR, GBP (default USD)
- `participants` (array, required): At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{"name":"Asha","paid":96},{"name":"Dev"}]
- `shares` (array): Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal split
- `total_cost` (number, required): Total court/venue cost in currency units, e.g. 96 for $96.00

Output parameters:

- `balances` (array): Per-player paid, owed share and net balance
- `currency` (string): Currency code used for display
- `note` (string): Plain-language summary of the settlement
- `total_cost` (number): Total shared cost, rounded to cents
- `transfer_count` (integer): Number of payments in transfers
- `transfers` (array): Minimal list of payments that settles the group

### `split_series` (~156 tokens)

Split series

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.

Input parameters:

- `currency` (string): Currency code used only for display, e.g. USD (default USD)
- `payments` (array): Optional list of who already paid what across the series, e.g. [{"name":"Asha","paid":120}]
- `players` (array): Optional full roster, so players who missed every session still appear with a zero balance
- `sessions` (array, required): Sessions in order, each with its cost and the names who attended

Output parameters:

- `currency` (string): Currency code used for display
- `note` (string): Explanation of how the series was split
- `players` (array): Per-player paid, owed, balance and sessions attended
- `session_count` (integer): Number of sessions processed
- `sessions` (array): Per-session cost breakdown
- `total_cost` (number): Sum of all session costs
- `transfers` (array): Fewest payments that settle everyone

### `rotation_plan` (~160 tokens)

Rotation plan

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.

Input parameters:

- `capacity` (integer, required): Players per court: 2 for singles, 4 for doubles, 10 for 5v5 basketball
- `courts` (integer): Number of courts in use at once (default 1)
- `players` (array, required): Unique roster names, at least capacity x courts of them, e.g. ["Asha","Dev","Mira","Sam","Lee","Kai"]
- `rounds` (integer, required): Number of rounds to schedule, 1-50

Output parameters:

- `fairness` (object): Games-played balance across the roster
- `format` (string): Format label with players per side and courts, e.g. '2v2 on 2 court(s)' for capacity 4 (doubles), '1v1' for capacity 2; odd capacity shows 'N player(s) per court'
- `note` (string): Whether the rotation is perfectly balanced
- `rounds` (integer): Number of rounds scheduled
- `schedule` (array): One entry per round

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/everyai-com-court-split/court-split#diagnostics

## Score history

- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-09: 73
- 2026-10-04: 68

## Common questions

### What is the CourtSplit MCP server?

CourtSplit is an MCP server listed in the public MCP registry as io.github.everyai-com/court-split. Split court costs, settle up and plan fair rotations for pickup games. Free. This page covers its hosted endpoint (https://court-split.magicteams.ai/mcp).

### Is the CourtSplit MCP server safe to use?

CourtSplit scores 77 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 CourtSplit MCP server expose?

CourtSplit exposes 4 tools: split_costs, settle_up, split_series, rotation_plan. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.

### Does the CourtSplit MCP server require authentication?

No. We connected to CourtSplit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CourtSplit MCP server still maintained?

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

## Links

- Remote endpoint: https://court-split.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-court-split/court-split.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-court-split/court-split.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-court-split/court-split