Name: xupersplit
Author: kanylbullen

xupersplit MCP

Split shared expenses in a group — no account needed. See who owes whom and settle up.

Tool-list grade A Remote · Streamable HTTP No auth needed 11 tools v1.0.1 MIT

No reviews yet by kanylbullenGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Split shared expenses in a group — no account needed. See who owes whom and settle up.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http xupersplit-mcp https://split.xuper.fun/api/mcp

# 2 — ask your agent for something these tools do
#   create_split, get_split, add_expense and 8 more

xupersplit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

kanylbullen1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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.

Parameter	Type	Required	Notes
title	string	yes	What the split is for, e.g. "Ski trip".
participants	array	yes	Names of everyone splitting, at least two.
currency	string	no	Currency code. Defaults to SEK.

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

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.

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

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
amount	number	yes	Amount in the split's currency, as a decimal (e.g. 249.50).
paid_by	string	yes	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
description	string	no	What it was, e.g. "Groceries".
split_between	array	no	Names of the people sharing this cost, split equally. Defaults to everyone.
shares	array	no	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.
date	string	no	Date as YYYY-MM-DD. Defaults to today.

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
from	string	yes	Who sent the money — a participant's name (or id) in this split.
to	string	yes	Who received it — a participant's name (or id) in this split.
amount	number	yes	Amount in the split's currency, as a decimal (e.g. 249.50).
description	string	no	How it was paid, e.g. "Swish, 3 March". Shown in the history.
date	string	no	Date as YYYY-MM-DD. Defaults to today.

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
entry_id	string	yes	The entry's id, from get_split.
amount	number	no	Amount in the split's currency, as a decimal (e.g. 249.50).
description	string	no	—
paid_by	string	no	Move the entry to a different payer.
to	string	no	New recipient — payments only.
split_between	array	no	Names of the people sharing this cost, split equally. Defaults to everyone.
shares	array	no	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.
date	string	no	Date as YYYY-MM-DD. Defaults to today.

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
entry_id	string	yes	The entry's id, from get_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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
name	string	yes	—

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
participant	string	yes	Who to rename — a participant's name (or id) in this split.
name	string	yes	The new name.

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
participant	string	yes	Who to remove — a participant's name (or id) in this split.

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
participant	string	yes	Whose details these are — a participant's name (or id) in this split.
methods	array	yes	—

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.

Parameter	Type	Required	Notes
split	string	yes	The split key, or the whole https://split.xuper.fun/k/<key> link.
title	string	no	—
currency	string	no	—

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install xupersplit or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.1 · scanned 20 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest27614719e010f321025d4f09c60601b44593313fa34968a67be09c9927299118

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
create_split	state-write	state-write: declares readOnlyHint: false
get_split	no tags
add_expense	state-write	state-write: declares readOnlyHint: false
record_payment	state-write	state-write: declares readOnlyHint: false
update_entry	state-write	state-write: declares readOnlyHint: false
delete_entry	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
add_participant	state-write	state-write: declares readOnlyHint: false
rename_participant	state-write	state-write: declares readOnlyHint: false
remove_participant	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
set_payment_methods	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
update_split	state-write	state-write: declares readOnlyHint: false

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest27614719e010f321

Scanned2026-10-20

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

xupersplit MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also