_ registry / mcp streamable-http · checked 3h ago

court-split

https://court-split.magicteams.ai

Registry code: ce588a63a1f4a530

api record

CourtSplit splits court and venue costs fairly, minimizes settle-up payments, accounts for recurring sessions with rotating attendance, and plans fair play rotations. All maths only; nothing stored.

endpoint
https://court-split.magicteams.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is court-split live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is court-split free to use?
Yes — the hub reached it with no key and no payment.
What tools does court-split have?
4 tools: rotation_plan, split_costs, split_series, settle_up.
Is court-split safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
318ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 390 checks · signed record
  • down → live
  • unknown → live
_ what it is for
used for
  • split court costs among players
  • compute minimal settle-up payments
  • split recurring session costs
  • plan fair play rotations
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • rotation_plan reads unknown 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "players",
        "capacity",
        "rounds"
      ],
      "properties": {
        "courts": {
          "type": "integer",
          "minimum": 1,
          "description": "Number of courts in use at once (default 1)"
        },
        "rounds": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Number of rounds to schedule, 1-50"
        },
        "players": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "minItems": 2,
          "description": "Unique roster names, at least capacity x courts of them, e.g. [\"Asha\",\"Dev\",\"Mira\",\"Sam\",\"Lee\",\"Kai\"]"
        },
        "capacity": {
          "type": "integer",
          "minimum": 1,
          "description": "Players per court: 2 for singles, 4 for doubles, 10 for 5v5 basketball"
        }
      }
    }
    arguments 34 lines
  • split_costs reads unknown 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "total_cost",
        "participants"
      ],
      "properties": {
        "shares": {
          "type": "array",
          "items": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "description": "Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal split"
        },
        "currency": {
          "type": "string",
          "description": "Currency code used only for display, e.g. USD, EUR, GBP (default USD)"
        },
        "total_cost": {
          "type": "number",
          "description": "Total court/venue cost in currency units, e.g. 96 for $96.00",
          "exclusiveMinimum": 0
        },
        "participants": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Player name, unique within the list, e.g. 'Asha'"
              },
              "paid": {
                "type": "number",
                "minimum": 0,
                "description": "Amount this player already paid toward the total, in currency units (default 0)"
              }
            }
          },
          "minItems": 2,
          "description": "At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{\"name\":\"Asha\",\"paid\":96},{\"name\":\"Dev\"}]"
        }
      }
    }
    arguments 48 lines
  • split_series reads unknown 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sessions"
      ],
      "properties": {
        "players": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional full roster, so players who missed every session still appear with a zero balance"
        },
        "currency": {
          "type": "string",
          "description": "Currency code used only for display, e.g. USD (default USD)"
        },
        "payments": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "paid"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Player who paid, e.g. the person who fronted court fees"
              },
              "paid": {
                "type": "number",
                "minimum": 0,
                "description": "Total amount this player has paid across the series, in currency units"
              }
            }
          },
          "description": "Optional list of who already paid what across the series, e.g. [{\"name\":\"Asha\",\"paid\":120}]"
        },
        "sessions": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "cost",
              "attendees"
            ],
            "properties": {
              "cost": {
                "type": "number",
                "description": "Cost of this session in currency units, e.g. 60",
                "exclusiveMinimum": 0
              },
              "label": {
                "type": "string",
                "description": "Optional session label, e.g. 'Tue 7pm' (default 'session N')"
              },
              "attendees": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "minItems": 1,
                "description": "Unique names of players present at this session"
              }
            }
          },
          "minItems": 1,
          "description": "Sessions in order, each with its cost and the names who attended"
        }
      }
    }
    arguments 72 lines
  • settle_up reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "total_cost",
        "participants"
      ],
      "properties": {
        "shares": {
          "type": "array",
          "items": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "description": "Optional positive relative weights, one per participant in the same order, e.g. [2,1,1]; omit for an equal split"
        },
        "currency": {
          "type": "string",
          "description": "Currency code used only for display, e.g. USD, EUR, GBP (default USD)"
        },
        "total_cost": {
          "type": "number",
          "description": "Total court/venue cost in currency units, e.g. 96 for $96.00",
          "exclusiveMinimum": 0
        },
        "participants": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Player name, unique within the list, e.g. 'Asha'"
              },
              "paid": {
                "type": "number",
                "minimum": 0,
                "description": "Amount this player already paid toward the total, in currency units (default 0)"
              }
            }
          },
          "minItems": 2,
          "description": "At least 2 players with unique names; include 'paid' for anyone who already paid, e.g. [{\"name\":\"Asha\",\"paid\":96},{\"name\":\"Dev\"}]"
        }
      }
    }
    arguments 48 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ce588a63a1f4a530.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ce588a63a1f4a530/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ce588a63a1f4a530/badge.svg)](https://brick.blue/agent/ce588a63a1f4a530?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on magicteams.ai 14 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

6 more sit on this domain. All of them.