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

xupersplit

https://split.xuper.fun

Registry code: cb7e1013be0adcae

api record

xupersplit splits shared expenses in a group — no accounts, no app. Create a split with create_split, then hand the returned link to the user so they can share it with the group; anyone holding that link can view and edit the split, so treat it as a secret. Add what people paid with add_expense, read who owes whom with get_split, and record paybacks with record_payment. Refer to people by name — the tools resolve names to participants for you. Working from a receipt or a photo of one: read it yourself and enter one expense per group of items sharing the same people, rather than one equal…

endpoint
https://split.xuper.fun/api/mcp
protocol
http-sse ·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 xupersplit live?
Yes — it answered the hub's last check (checked 3h ago). It answered 98% of checks over the last 30 days.
Is xupersplit free to use?
Yes — the hub reached it with no key and no payment.
What tools does xupersplit have?
11 tools: create_split, add_expense, record_payment, update_entry, rename_participant, remove_participant, set_payment_methods, delete_entry, ….
Is xupersplit 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
98.2%

90 days 98.5%· all time 98.5%

latency
646ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 406 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce
used for
  • create a shared expense split
  • add an expense to a split
  • see who owes whom
  • record a payback
  • set payment methods for a person
takes → gives
text, data → data
tools
1 reads10 changes data
_ 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 11 tools
11 never probed 0 of 11 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.

  • create_split changes data unknown never probed

    Create a new xupersplit for sharing expenses in a group. No account needed. Returns a secret link — give it to the user and tell them to share it with the group, since anyone holding the link can see and edit the split.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "title",
    "participants"
  ],
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "description": "What the split is for, e.g. \"Ski trip\"."
    },
    "currency": {
      "enum": [
        "SEK",
        "EUR",
        "USD",
        "NOK",
        "DKK",
        "ISK",
        "GBP",
        "CHF",
        "PLN",
        "THB",
        "SATS"
      ],
      "type": "string",
      "description": "Currency code. Defaults to SEK."
    },
    "participants": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "minItems": 2,
      "description": "Names of everyone splitting, at least two."
    }
  }
}
    arguments 41 lines
  • add_expense changes data unknown never probed

    Record something one person paid for the group. Split equally by default; pass split_between for a subset, or shares for an uneven split. One expense covers one set of people — a receipt whose items aren't all shared by everyone is several expenses, so call this once per group of items that the same people share, rather than splitting the total equally. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "amount",
    "paid_by"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date as YYYY-MM-DD. Defaults to today."
    },
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "amount": {
      "type": "number",
      "description": "Amount in the split's currency, as a decimal (e.g. 249.50).",
      "exclusiveMinimum": 0
    },
    "shares": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "participant"
        ],
        "properties": {
          "amount": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "weight": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "participant": {
            "type": "string"
          }
        }
      },
      "description": "Uneven split. Either an exact `amount` per person (must add up to the total) or a relative `weight` per person (e.g. weight 2 for a couple). Don't combine with split_between."
    },
    "paid_by": {
      "type": "string",
      "description": "Who paid — a participant's name (or id) in this split. A card receipt rarely names the payer, so ask unless you know: guess wrong and every balance points the wrong way. If the user counts themselves among the participants, assume it was them and say that you assumed it — what you must not do is pick a payer silently."
    },
    "description": {
      "type": "string",
      "description": "What it was, e.g. \"Groceries\"."
    },
    "split_between": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Names of the people sharing this cost, split equally. Defaults to everyone."
    }
  }
}
    arguments 62 lines
  • record_payment changes data unknown never probed

    Record that one person paid another back, settling part or all of a debt. Use get_split first to see who should pay whom. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "from",
    "to",
    "amount"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Who received it — a participant's name (or id) in this split."
    },
    "date": {
      "type": "string",
      "description": "Date as YYYY-MM-DD. Defaults to today."
    },
    "from": {
      "type": "string",
      "description": "Who sent the money — a participant's name (or id) in this split."
    },
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "amount": {
      "type": "number",
      "description": "Amount in the split's currency, as a decimal (e.g. 249.50).",
      "exclusiveMinimum": 0
    },
    "description": {
      "type": "string",
      "description": "How it was paid, e.g. \"Swish, 3 March\". Shown in the history."
    }
  }
}
    arguments 37 lines
  • update_entry changes data unknown never probed

    Change an existing expense or payment. Only the fields you pass are changed. Entry ids come from get_split. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "entry_id"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "New recipient — payments only."
    },
    "date": {
      "type": "string",
      "description": "Date as YYYY-MM-DD. Defaults to today."
    },
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "amount": {
      "type": "number",
      "description": "Amount in the split's currency, as a decimal (e.g. 249.50).",
      "exclusiveMinimum": 0
    },
    "shares": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "participant"
        ],
        "properties": {
          "amount": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "weight": {
            "type": "number",
            "exclusiveMinimum": 0
          },
          "participant": {
            "type": "string"
          }
        }
      },
      "description": "Uneven split. Either an exact `amount` per person (must add up to the total) or a relative `weight` per person (e.g. weight 2 for a couple). Don't combine with split_between."
    },
    "paid_by": {
      "type": "string",
      "description": "Move the entry to a different payer."
    },
    "entry_id": {
      "type": "string",
      "description": "The entry's id, from get_split."
    },
    "description": {
      "type": "string"
    },
    "split_between": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Names of the people sharing this cost, split equally. Defaults to everyone."
    }
  }
}
    arguments 68 lines
  • rename_participant changes data unknown never probed

    Change a participant's name. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "participant",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "The new name."
    },
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "participant": {
      "type": "string",
      "description": "Who to rename — a participant's name (or id) in this split."
    }
  }
}
    arguments 24 lines
  • remove_participant changes data unknown never probed

    Remove someone from a split. Only works if they aren't on any expense yet. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "participant"
  ],
  "properties": {
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "participant": {
      "type": "string",
      "description": "Who to remove — a participant's name (or id) in this split."
    }
  }
}
    arguments 18 lines
  • set_payment_methods changes data unknown never probed

    Set how a participant wants to be paid back, so the split can show a QR code or pay link. Replaces their current list (pass an empty array to clear it). Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "participant",
    "methods"
  ],
  "properties": {
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "methods": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "value"
        ],
        "properties": {
          "type": {
            "enum": [
              "swish",
              "vipps",
              "mobilepay",
              "revolut",
              "lightning",
              "evm",
              "solana",
              "iban"
            ],
            "type": "string"
          },
          "value": {
            "type": "string",
            "description": "Phone number for swish/vipps/mobilepay, IBAN, Revolut tag, Lightning address, 0x/ENS address, or Solana address."
          }
        }
      },
      "maxItems": 8
    },
    "participant": {
      "type": "string",
      "description": "Whose details these are — a participant's name (or id) in this split."
    }
  }
}
    arguments 49 lines
  • delete_entry changes data unknown never probed

    Remove an expense or payment for good. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "entry_id"
  ],
  "properties": {
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "entry_id": {
      "type": "string",
      "description": "The entry's id, from get_split."
    }
  }
}
    arguments 18 lines
  • add_participant changes data unknown never probed

    Add someone to an existing split. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1
    },
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    }
  }
}
    arguments 18 lines
  • update_split changes data unknown never probed

    Change a split's title or currency. The currency is locked once the split has expenses. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split"
  ],
  "properties": {
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    },
    "title": {
      "type": "string",
      "minLength": 1
    },
    "currency": {
      "enum": [
        "SEK",
        "EUR",
        "USD",
        "NOK",
        "DKK",
        "ISK",
        "GBP",
        "CHF",
        "PLN",
        "THB",
        "SATS"
      ],
      "type": "string"
    }
  }
}
    arguments 33 lines
  • get_split reads unknown 19h ago

    Read a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "split"
  ],
  "properties": {
    "split": {
      "type": "string",
      "description": "The split key, or the whole https://split.xuper.fun/k/<key> link."
    }
  }
}
    arguments 13 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 cb7e1013be0adcae.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cb7e1013be0adcae/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/cb7e1013be0adcae/badge.svg)](https://brick.blue/agent/cb7e1013be0adcae?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
100%

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.