xupersplit MCP server
online · 100% uptimeio.github.kanylbullen/xupersplit·v1.0.1·4 starsSplit shared expenses in a group — no account needed. See who owes whom and settle up.
4 stars
Reviews
Write oneNobody has reviewed xupersplit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
xupersplit tools (11, 5 write)
write = sends, deletes, buys or postsadd_expenseFreeRecord 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.
add_participantFreeAdd 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.
create_splitwrite actionFreeCreate 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.
delete_entrywrite actionFreeRemove 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.
get_splitFreeRead a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up.
record_paymentFreeRecord 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.
remove_participantwrite actionFreeRemove 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.
rename_participantFreeChange 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.
set_payment_methodsFreeSet 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.
update_entrywrite actionFreeChange 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.
update_splitwrite actionFreeChange 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.
Public scan report
scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1215ms20/20
- Tool poisoning11 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
- Maintenancelast push 16 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How xupersplit compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 62% of 48,255 servers
- Tools
- 11
- the typical server has 7
- Tools that change things
- 45%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 154 ms
- faster than 72% of 30,031 servers
- GitHub stars
- 4
- more than 82% of 28,688 servers
What its tools let an agent do: 2 read · 3 create · 4 change · 2 delete
Install xupersplit in Claude Code, Cursor or VS Code
claude mcp add --transport http xupersplit https://split.xuper.fun/api/mcp
What the publisher says
From the xupersplit repository's README, as published. We do not edit it. Read it on GitHub
xupersplit
Split shared expenses without the fuss. Create a split, share the link, and let everyone add what they paid — balances and who-owes-whom are worked out automatically, with one-tap payments straight from the balance view.
split.xuper.fun · English · Svenska
Next.js 16 · Supabase · Tailwind v4 · wagmi/viem
Create a split and see who owes whom · a Swish QR with the amount already in it · splitting by shares
Works with AI agents. xupersplit is an MCP server too —
point your assistant at one URL and it can create the split, add what everyone
paid and tell you who owes whom. No account, no API key, nothing to install.
claude mcp add --transport http xupersplit https://split.xuper.fun/api/mcp
What it is
A clean, accountless expense splitter. The secret link is the key — anyone with it can add expenses and settle up; no login required. Optional email sign-in just makes your splits follow you across devices. Built as a one-prompt project and grown from there.
Features
the capability. Sign-in is optional.
- No account needed. The unguessable split link (122 bits of entropy) is
rounding via the largest-remainder method.
- Flexible splitting — equal, weighted shares, or exact amounts, with cent
partial payments ("pay all or part") and strike-through once settled.
- Smart settlements — the minimum set of "A pays B" transfers, with
themselves done; the pay dialog warns if someone hasn't weighed in yet.
- Don't settle too early — see who has opened the split and who's marked
accounts: you can only edit your own payment details and enter your own expenses. The creator picks who must log in, who can view, and how people join.
- Secure splits (optional, when signed in) — bind participants to their
save (Kittysplit-style); set a main currency per split. Includes sats** — run a whole split in bitcoin if you like.
- Multi-currency — enter expenses in any currency with the rate **locked at
Model Context Protocol, with no account and no API key.
- Eight payment methods, several with genuine one-tap prefill — see below.
- MCP server — AI agents can run a whole split over
(auto-detected, switchable).
- Six languages — English, Svenska, Norsk, Dansk, Suomi, Íslenska
inactive splits are purged after 6 months, IP hashes deleted within a day, CSV/JSON export, full GDPR policy.
- Privacy by design — payment details can be wiped once everyone is square,
- Dark / light / system theme, cookie-less analytics, discreet cookie notice.
Payments
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
xupersplit: common questions
- Is xupersplit MCP server safe?
- Mostly: it is graded B (81/100). Read the xupersplit safety report
- How do I install xupersplit?
- It runs remotely at split.xuper.fun. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does xupersplit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is xupersplit maintained?
- The last commit was 58 days ago (2026-09-07). The latest release is v1.0.1.
- Is xupersplit up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does xupersplit compare with other MCP servers?
- safety score 81/100 (higher than 62% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 45% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.