xupersplit

io.github.kanylbullen由 GitHub 账号 kanylbullen 发布v1.0.1更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行效率与工作流金融

概览

AI 生成的概览

免账号的群组分账工具:助手可创建分账、记录支出与还款,并给出谁欠谁的结算方案和分享链接。

可以做什么
  • 创建分账并返回需要分享的秘密链接
  • 读取分账的参与者、支出、每人余额以及最少的结算转账
  • 新增、修改和删除支出与还款,支持均分、指定子集或按份额分摊
  • 添加、重命名或移除参与者,并设置其收款方式
  • 修改分账的标题或货币
适用场景
适合一群人需要记录共同开销(旅行、聚餐、合租账单)时,由助手代为记账并算出结算方案,再把一个链接发给所有人。无需注册,适合临时、非正式的分账。
运行要求
远程 Streamable HTTP 端点,无需账号、API 密钥或安装。仅支持 stdio 的客户端需借助 mcp-remote 之类的桥接。在 ChatGPT 中需先开启开发者模式才能添加为连接器。
安装前请注意
秘密链接就是唯一凭证:任何持有链接的人都能查看和编辑该分账,包括收款信息,应视为敏感信息。修改和删除不可恢复。收款方式可被任何持链接者更改,加密货币付款不可撤销。登录用户创建的“安全分账”通过 MCP 只能读取。

安装

在 SourceWeft 中

  1. 打开 控制台中的 xupersplit,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.kanylbullen%2Fxupersplit/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

来源:README.md,提交 ac4e281

工具

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.

输入参数title必填currencyparticipants必填

get_split

Read a split

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

输入参数split必填

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.

输入参数datesplit必填amount必填sharespaid_by必填descriptionsplit_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.

输入参数to必填datefrom必填split必填amount必填description

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.

输入参数todatesplit必填amountsharespaid_byentry_id必填descriptionsplit_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.

输入参数split必填entry_id必填

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.

输入参数name必填split必填

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.

输入参数name必填split必填participant必填

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.

输入参数split必填participant必填

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.

输入参数split必填methods必填participant必填

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.

输入参数split必填titlecurrency

版本历史

1
  1. v1.0.1最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分