A
licenseC
qualityC
maintenanceEnables turning receipt photos into checked, per-person expense splits with exact-cent reconciliation.
5
MIT
xupersplit
Server Details
Split shared expenses in a group — no account needed. See who owes whom and settle up.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- kanylbullen/xupersplit
- GitHub Stars
- 4
- Server Listing
- xupersplit
- ChatGPT
- –
- Claude
- –
TDQS
A4.1/5.0
Scored across 11 tools
Disambiguation4/5
Most tools target a distinct resource+action pair, and the descriptions carefully separate add_expense (one person fronted money for the group) from record_payment (settling a debt between two people). The only mild confusion is the generic 'entry' used by update_entry/delete_entry versus 'expense' in add_expense, though descriptions clarify that entries include payments.
Naming Consistency4/5
All names follow snake_case verb_noun (create_split, add_participant, rename_participant, set_payment_methods, update_split), which is highly predictable. Minor deviation: add_expense/record_payment introduce short-lived nouns while updates/deletes operate on the generic 'entry', so the noun vocabulary shifts slightly across the lifecycle.
Tool Count5/5
11 tools is squarely in the well-scoped range for a group-expense-splitting domain. Each tool maps to a real operation (split lifecycle, participant management, expense/payment lifecycle, payout details) and none feel redundant.
Completeness4/5
Full lifecycle coverage for splits (create/get/update), participants (add/remove/rename), entries (add/update/delete via get_split), and payments (record + update_entry/delete_entry). The notable gap is the absence of a delete_split or a way to list/find splits without the secret link, which leaves a dead end for cleanup and discovery.
Available Tools
11 toolsadd_expenseAdd an expenseAInspect
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.
Inputs: split (required), amount (required), paid_by (required), date, +3 more. Returns: key, url, title, secure, +7 more
add_participantAdd a participantAInspect
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.
Inputs: name (required), split (required). Returns: key, url, title, secure, +7 more
create_splitCreate a splitAInspect
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.
Inputs: title (required), participants (required), currency. Returns: key, url, title, secure, +7 more
delete_entryDelete an entryADestructiveInspect
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.
Inputs: split (required), entry_id (required). Returns: key, url, title, secure, +7 more
get_splitRead a splitARead-onlyInspect
Read a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up.
Inputs: split (required). Returns: key, url, title, secure, +7 more
record_paymentRecord a paymentAInspect
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.
Inputs: to (required), from (required), split (required), amount (required), +2 more. Returns: key, url, title, secure, +7 more
remove_participantRemove a participantADestructiveInspect
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.
Inputs: split (required), participant (required). Returns: key, url, title, secure, +7 more
rename_participantRename a participantAInspect
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.
Inputs: name (required), split (required), participant (required). Returns: key, url, title, secure, +7 more
set_payment_methodsSet payment detailsADestructiveInspect
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.
Inputs: split (required), methods (required), participant (required). Returns: key, url, title, secure, +7 more
update_entryUpdate an entryAInspect
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.
Inputs: split (required), entry_id (required), to, date, +5 more. Returns: key, url, title, secure, +7 more
update_splitRename a splitAInspect
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.
Inputs: split (required), title, currency. Returns: key, url, title, secure, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Split shared costs fairly: who owes whom, in the fewest payments. No account.
Track and split shared expenses across trips, events, and groups. Create groups, add expenses, and…
Split the bill without the awkward math.
Track shared expenses, payments and balances across BananaSplit groups and friends.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables group expense management and fair settlement via MCP, allowing creation of groups, recording expenses, viewing balances, and computing minimal transfers to settle debts.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables conversational control of Splitwise accounts through Claude AI, allowing users to add expenses, check group balances, record settlements, and manage payment splits using natural language commands. Supports multiple currencies and flexible splitting methods including equal, exact, and percentage-based divisions.1MIT
- AlicenseAqualityBmaintenanceEnables natural-language interaction with Splitwise to explain balances, find missing or duplicate expenses, plan settlements, and safely add expenses with confirmation.1011 npmMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.