xupersplit MCP server
io.github.kanylbullen/xupersplitkanylbullenstreamable-httpv1.0.1Scanned
Split shared expenses in a group — no account needed. See who owes whom and settle up.
11 tools: 3 can delete or cancel things, 2 do something that can't be undone, 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the xupersplit MCP server can do
The xupersplit MCP server is published by the GitHub account kanylbullen. It has 11 tools. It can delete or cancel things (3 tools: delete_entry, remove_participant and set_payment_methods), do things that cannot be undone, such as sending, paying or publishing (record_payment and update_entry) and create or change data (5 tools: create_split, add_expense, add_participant, rename_participant and 1 more). 1 tool only reads.
2 tools can send data out of your system (record_payment and update_entry).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 3Claude Code: deny
delete_entryRemove an expense or payment for good.No findings
Why it is in this group
- The name "delete_entry" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
remove_participantRemove someone from a split.No findings
Why it is in this group
- The name "remove_participant" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
set_payment_methodsSet how a participant wants to be paid back, so the split can show a QR code or pay link.No findings
Why it is in this group
- The name "set_payment_methods" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
Can't be undone 2Claude Code: ask
record_paymentRecord that one person paid another back, settling part or all of a debt.Can send data outNo findings
Why it is in this group
- The name "record_payment" says "payment": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
update_entryChange an existing expense or payment.Can send data outNo findings
Why it is in this group
- The name "update_entry" says "update": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Changes things 5Claude Code: ask
add_expenseRecord something one person paid for the group.No findings
Why it is in this group
- The name "add_expense" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
add_participantAdd someone to an existing split.No findings
Why it is in this group
- The name "add_participant" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
create_splitCreate a new xupersplit for sharing expenses in a group.No findings
Why it is in this group
- The name "create_split" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
rename_participantChange a participant's name.No findings
Why it is in this group
- The name "rename_participant" says "rename": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
update_splitChange a split's title or currency.No findings
Why it is in this group
- The name "update_split" says "update": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 1Show 1 read-only tool
get_splitRead a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up.No findings
Why it is in this group
- The name "get_split" says "get": a word for reading.
Description, as the server wrote it Read a split: participants, expenses, per-person balances and the shortest set of payments that settles everyone up.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (3 destructive, 2 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://split.xuper.fun/api/mcp: tools/list returned 11 tools to an anonymous client, including delete_entry (destructive), remove_participant (destructive), set_payment_methods (destructive), record_payment (irreversible), update_entry (irreversible) and 5 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http xupersplit https://split.xuper.fun/api/mcpclaude mcp add --transport http xupersplit https://split.xuper.fun/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__xupersplit__get_split"
],
"ask": [
"mcp__xupersplit__create_split",
"mcp__xupersplit__add_expense",
"mcp__xupersplit__record_payment",
"mcp__xupersplit__update_entry",
"mcp__xupersplit__add_participant",
"mcp__xupersplit__rename_participant",
"mcp__xupersplit__update_split"
],
"deny": [
"mcp__xupersplit__delete_entry",
"mcp__xupersplit__remove_participant",
"mcp__xupersplit__set_payment_methods"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as xupersplit. Review it before you use it.
Capability tags behind 2 rules
- mcp__xupersplit__record_payment outbound
- mcp__xupersplit__update_entry outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kanylbullen/xupersplit/verify?hash=52be571ecdb3dbdb2401316aabe01d686d839c685890efeaddca99766c5f9043" | jq -e '.changed == false'Pinned hash 52be571ecdb3, from Nov 20, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kanylbullen/xupersplit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kanylbullen/xupersplit)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
xupersplit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the xupersplit MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the xupersplit MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: delete_entry, remove_participant and set_payment_methods.
Can the xupersplit MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: record_payment and update_entry.
What tools does the xupersplit MCP server have?
- 11 tools: 3 destructive, 2 irreversible, 5 write, 1 read. delete_entry, remove_participant, set_payment_methods, record_payment, update_entry, create_split, add_expense, add_participant and 3 more.
Does the xupersplit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the xupersplit MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): record_payment and update_entry.
Has the xupersplit MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.