mcp server
Xupersplit
Split shared expenses in a group — no account needed. See who owes whom and settle up.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-08-03.
What this server can do
11 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
add_expense(date, split, amount, shares, paid_by, description, split_between)- 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. Required: split, amount, paid_by.
add_participant(name, split)- 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. Required: split, name.
create_split(title, currency, participants)- 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. Required: title, participants.
delete_entry(split, entry_id)- 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. Required: split, entry_id.
get_split(split)- Read a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up. Required: split.
record_payment(to, date, from, split, amount, description)- 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. Required: split, from, to, amount.
remove_participant(split, participant)- 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. Required: split, participant.
rename_participant(name, split, participant)- 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. Required: split, participant, name.
set_payment_methods(split, methods, participant)- 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. Required: split, participant, methods.
update_entry(to, date, split, amount, shares, paid_by, entry_id, description, split_between)- 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. Required: split, entry_id.
update_split(split, title, currency)- 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. Required: split.
Last successful function declaration observed on . Source: https://split.xuper.fun/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://split.xuper.fun/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 11 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | split.xuper.fun | |
| mcp endpoint status | ok | The server listed 11 functions when asked. | as of probe | split.xuper.fun |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json