Skip to content
External endpointresponds

Xupersplit

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

Endpoint URL
https://split.xuper.fun/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
227 ms
Response record
2 of 2 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.kanylbullen/xupersplit

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
xupersplit
Version
1.0.1
Capability keys
tools
Tool names
create_split, get_split, add_expense, record_payment, update_entry, delete_entry, add_participant, rename_participant, remove_participant, set_payment_methods, update_split
Instructions excerpt

xupersplit splits shared expenses in a group — no accounts, no app. Create a split with create_split, then hand the returned link to the user so they can share it with the group; anyone holding that link can view and edit the split, so treat it as a secret. Add what people paid with add_expense, read who owes whom with get_split, and record paybacks with record_payment. Refer to people by name — the tools resolve names to participants for you. Working from a receipt or a photo of one: read it yourself and enter one expense per group of items sharing the same people, rather than one equal split of the total — the shared bottle of wine and the individual mains are separate expenses. When you cannot tell who had what, ask rather than spreading that line evenly; an even split you already suspect is wrong costs the group real money and looks authoritative doing it. The tell is that the counts don't fit the group — two glasses of wine for three people, one dessert for four. Name the

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 155ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 227ms