xupersplit

io.github.kanylbullenPublished by GitHub account kanylbullenv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFinance

Overview

AI-generated overview

Accountless group expense splitter: an assistant can create a split, log expenses and payments, and report who owes whom via a secret link.

What you can do
  • Create a split and hand back the secret share link
  • Read a split's participants, expenses, per-person balances and the minimum settling payments
  • Add, edit and delete expenses and repayments, split equally, by subset or by shares
  • Add, rename or remove participants, and set their payment handles
  • Change a split's title or currency
When to use it
Useful when a group wants to track shared costs (trips, dinners, shared bills) and have the assistant do the bookkeeping and settle-up math, then share one link with everyone. Works without sign-up, so it suits quick, informal splits.
Requirements
A remote Streamable HTTP endpoint; no account, API key or installation needed. Stdio-only clients need a bridge such as mcp-remote. ChatGPT requires developer mode to add it as a connector.
Before you install
The secret link is the only credential: anyone holding it can view and edit the split, including payment details, so treat it as sensitive. Edits and deletions are permanent. Payment handles can be changed by anyone with the link, and crypto payments are irreversible. Secure splits made by signed-in users are read-only over MCP.

Installation

In SourceWeft

  1. Open xupersplit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kanylbullen%2Fxupersplit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "xupersplit": {
      "type": "http",
      "url": "https://split.xuper.fun/api/mcp"
    }
  }
}

README

[xupersplit — split expenses, skip the fuss]

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

[CI]  [License: MIT]  [MCP registry]  [Live app]

Next.js 16 · Supabase · Tailwind v4 · wagmi/viem


[xupersplit demo — create a split, add an expense, then settle up onchain in USDC]   [Pay dialog: a Swish QR with the exact amount already filled in]   [New expense: splitting by shares, a couple counting double]

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

  • No account needed. The unguessable split link (122 bits of entropy) is the capability. Sign-in is optional.
  • Flexible splitting — equal, weighted shares, or exact amounts, with cent rounding via the largest-remainder method.
  • Smart settlements — the minimum set of "A pays B" transfers, with partial payments ("pay all or part") and strike-through once settled.
  • Don't settle too early — see who has opened the split and who's marked themselves done; the pay dialog warns if someone hasn't weighed in yet.
  • Secure splits (optional, when signed in) — bind participants to their 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.
  • Multi-currency — enter expenses in any currency with the rate locked at save (Kittysplit-style); set a main currency per split. Includes sats — run a whole split in bitcoin if you like.
  • Eight payment methods, several with genuine one-tap prefill — see below.
  • MCP server — AI agents can run a whole split over Model Context Protocol, with no account and no API key.
  • Six languages — English, Svenska, Norsk, Dansk, Suomi, Íslenska (auto-detected, switchable).
  • Privacy by design — payment details can be wiped once everyone is square, inactive splits are purged after 6 months, IP hashes deleted within a day, CSV/JSON export, full GDPR policy.
  • Dark / light / system theme, cookie-less analytics, discreet cookie notice.

Payments

xupersplit stores each recipient's payment handle(s) and, wherever a payment network exposes an open, agreement-free interface, turns the balance row into a real one-tap payment — prefilled with the exact amount. No money ever passes through xupersplit; it only builds the link/invoice/transaction the payer approves in their own app.

MethodExperienceHow
Swish 🇸🇪QR + app deep link, amount prefilledPublic app.swish.nu link + QR endpoint — no merchant contract
Lightning ⚡QR + lightning: link, exact amount baked inLNURL-pay (LUD-16): a lightning address → BOLT11 invoice
Ethereum / USDC ΞOne-tap prefilled USDC transferWalletConnect (Reown AppKit) — connect, pick chain, approve
Solana / USDC ◎One-tap prefilled USDC SPL transferWalletConnect (Reown AppKit) — Phantom/Solflare, recipient ATA auto-created
Ethereum / Solana addressAddress QR + copy, ENS resolved0x… / name.eth / base58 — for any wallet
RevolutClickable revolut.me profile linkOpens the recipient's profile to pay
Vipps · MobilePay · IBANStored handle + copy buttonNo open P2P API — the payer finishes in their own app

Why the difference? Swish exposes a genuinely open prefilled deep link and QR endpoint; Lightning's LNURL and EVM/Solana over WalletConnect are open protocols. Vipps and MobilePay (now Vipps MobilePay) only offer amount-prefilled flows through their merchant APIs — a business agreement that routes money to a company, not person-to-person — so for those xupersplit does the honest thing and shows the handle with a copy button. If they ever ship an open P2P deep link, wiring it in is a small change. PRs welcome. 🤞

Crypto is irreversible. Crypto methods show extra warnings, and any method warns (with a date) if the recipient's details were ever changed from what was first entered — anyone with the link can edit them.

MCP server

xupersplit speaks Model Context Protocol, so an AI assistant can create a split, add what everyone paid and report who owes whom — then hand you the link to share. Accountless like the rest of the app: no sign-up, no API key.

bash
claude mcp add --transport http xupersplit https://split.xuper.fun/api/mcp

Or point any MCP client at https://split.xuper.fun/api/mcp (Streamable HTTP; stdio-only clients can bridge via npx mcp-remote). Self-hosted instances get the same endpoint at their own /api/mcp.

It also works as a custom connector in Claude and ChatGPT on the web — paste the endpoint, no authentication. ChatGPT needs developer mode switched on first, or the option to add one isn't there at all. Step-by-step at /mcp.

Eleven tools cover the whole lifecycle — create_split, get_split, add_expense, record_payment, update_entry, delete_entry, add_participant, rename_participant, remove_participant, set_payment_methods, update_split. People are referred to by name and amounts are plain decimals, so an agent never handles uuids or cents.

The server is a thin layer over the same RPCs and money.ts helpers the web app uses, and it only ever holds the anonymous role — which is what keeps secure splits (they need a signed-in auth.uid()) unreachable over MCP. Full details at /mcp.

Architecture

  • No service-role key in the app. All data access goes through security definer Postgres RPCs (split_data, save_entry, set_payment_methods, …) where the secret split key in the URL is the capability. RLS is deny-all on every table and direct grants are revoked — the client only ever holds the public publishable key. Schema and every change live in supabase/migrations/.
  • Next.js App Router + server actions; the client is plain React, no state library. Tailwind v4 with CSS-variable theming.
  • Thin, keyless API routes proxy the open payment networks, all same-origin-locked: /api/swish-qr, /api/ln-invoice (LNURL-pay), /api/ens (viem), /api/fx (fiat + BTC, with provider fallback).
  • WalletConnect is fully gated on a project id — absent, the EVM dialog cleanly falls back to QR + copy.
  • Privacy & abuse controls — settle-time payment wipe (opt-out), 6-month purge of inactive splits, per-IP-hash + global create rate limits, and a daily job that flags split-key enumeration attempts.

Tech stack

Next.js 16 · React 19 · TypeScript · Tailwind CSS v4 · Supabase (Postgres, Auth) · wagmi + viem + @solana/web3.js + Reown AppKit · Playwright · Vercel

Run it locally

bash
npm installcp .env.example .env.local   # add your own Supabase URL + anon keynpm run dev

.env.local:

NEXT_PUBLIC_SUPABASE_URL=https://<your-project>.supabase.coNEXT_PUBLIC_SUPABASE_ANON_KEY=<your publishable key># Optional — enables the WalletConnect USDC flow (free id from cloud.reown.com)NEXT_PUBLIC_REOWN_PROJECT_ID=<your reown project id>

Deploy your own

Self-hostable on the free tiers of Supabase + Vercel.

  1. Supabase — create a project (EU regions keep data in Europe), then apply the schema with supabase link --project-ref <ref> && supabase db push (runs every migration in supabase/migrations/). Grab the Project URL and publishable (anon) key. For optional email sign-in, configure SMTP and the …/auth/confirm redirect.
  2. Vercel — import the repo, add NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY (both safe to expose; security relies on RLS
    • RPCs). Add NEXT_PUBLIC_REOWN_PROJECT_ID too if you want WalletConnect. Deploy.
  3. Custom domain (optional) — add it in Vercel, point a DNS-only CNAME to cname.vercel-dns.com, and add the domain's …/auth/confirm to the Supabase redirect allowlist if using email sign-in.

Full self-host with Docker

Prefer to own the whole stack? selfhost/ brings up the app and its own backend — Postgres, auth (GoTrue), the REST/RPC layer (PostgREST) and a local mailbox — with no external services. The app itself acts as the gateway, so the browser only ever talks to one origin.

bash
cd selfhostcp .env.example .env       # ⚠️ change the secrets — see the notes in the filedocker compose up -d --build
  • App: http://localhost:3000. Sign in with email + password (works instantly, no SMTP needed) — or use the magic code, which lands in Mailpit at http://localhost:8025.
  • HTTPS is one flag away: point a domain at the host, set DOMAIN + ACME_EMAIL and SITE_URL=https://… in .env, then docker compose --profile tls up -d --build — Caddy fetches and renews a Let's Encrypt certificate automatically. Behind NAT or want a wildcard cert? Set CF_API_TOKEN (a scoped Cloudflare token) and Caddy uses the DNS-01 challenge instead — no port 80 exposure needed.
  • The migrations in supabase/migrations/ are applied automatically on first start.
  • .env.example ships with public demo JWT keys so it runs out of the box. For anything internet-facing, change JWT_SECRET + the passwords and regenerate ANON_KEY/SERVICE_ROLE_KEY (any JWT tool works — sign {"role":"anon",...} / {"role":"service_role",...} with the new secret).
  • Set APP_PORT / MAILPIT_PORT in .env to change host ports; REOWN_PROJECT_ID enables the WalletConnect pay buttons.

See selfhost/README.md for the full guide — secret regeneration, the gateway architecture, Cloudflare DNS-01, a config reference and troubleshooting.

Tests & CI

Playwright smoke tests (npm run test:e2e) run on every PR against a local production build, gating merges to main; the pure split/balance/settlement logic lives in src/lib/money.ts.

Contributing

Issues and PRs are welcome, and so is a bug report from someone who just used the site. Start with CONTRIBUTING.md.

Never post a split link. A split's URL is its password — anyone who sees it can read and edit that split, and issues are public and indexed. Describe the problem, or make a throwaway split with fake names.

Most wanted right now: a real open P2P deep link for Vipps or MobilePay so the amount can be prefilled the way Swish and Lightning already do, plus additional payment rails and translation fixes across the six locales. The codebase is small and fully typed.

License

MIT — see LICENSE.


If xupersplit saved your group some bickering, you can

[Buy me a beer]

built with love, coffee and beer

Source: README.md at commit ac4e281

Tools

11

create_split

Create a split

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.

Parameterstitlerequiredcurrencyparticipantsrequired

get_split

Read a split

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

Parameterssplitrequired

add_expense

Add an expense

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.

Parametersdatesplitrequiredamountrequiredsharespaid_byrequireddescriptionsplit_between

record_payment

Record a payment

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.

Parameterstorequireddatefromrequiredsplitrequiredamountrequireddescription

update_entry

Update an entry

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.

Parameterstodatesplitrequiredamountsharespaid_byentry_idrequireddescriptionsplit_between

delete_entry

Delete an entry

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.

Parameterssplitrequiredentry_idrequired

add_participant

Add a participant

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.

Parametersnamerequiredsplitrequired

rename_participant

Rename a participant

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.

Parametersnamerequiredsplitrequiredparticipantrequired

remove_participant

Remove a participant

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.

Parameterssplitrequiredparticipantrequired

set_payment_methods

Set payment details

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.

Parameterssplitrequiredmethodsrequiredparticipantrequired

update_split

Rename a split

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.

Parameterssplitrequiredtitlecurrency

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts