splitbill MCP server
com.jittee/splitbilljittee.comstreamable-httpv1.0.7Scanned
Split bills and collect payments through PayNow (Singapore) from your AI. MCP server for SplitBill.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the splitbill MCP server can do
The splitbill MCP server is published by jittee.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: create_split), but cannot delete data. 2 tools only read.
1 tool reads private data (get_split); 1 tool brings in text other people can write (list_splits).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 29, 2026, version 1.0.7.
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.
3 tools
Changes things 1Claude Code: ask
create_splitCreate a payment page for a shared bill and return the manage URL plus the share URLs.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 payment page for a shared bill and return the manage URL plus the share URLs. The PayNow recipient is already saved with this connection — never ask the user for it. All you need is a total (total) or the receipt lines (items), plus the head count (people). Children can pay half: "4 adults and 3 kids" is people=7 with children=3. By default the user is treated as having paid up front: they count towards the head count but get no payment link (pass i_paid=false to turn that off). Paste a share URL into the group chat and everyone sees their own amount and a PayNow QR code.
Annotations the server declares
- title: Create a split bill
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_splitReturn one split in full: who owes what, whether they have paid, the notes they left, and the share URLs.Reads private dataNo findings
Why it is in this group
- The name "get_split" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "note": it reads notes.
Description, as the server wrote it Return one split in full: who owes what, whether they have paid, the notes they left, and the share URLs.
Annotations the server declares
- title: Check how a split is going
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_splitsReturn the splits created with this connection, newest first, with how much has been collected, how many people are still to pay, and the read-only URL.Reads text others writeNo findings
Why it is in this group
- The name "list_splits" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Return the splits created with this connection, newest first, with how much has been collected, how many people are still to pay, and the read-only URL. Use this to find a split again when the organiser has lost the link.
Annotations the server declares
- title: List the splits made with this connection
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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, 18:40 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://jittee.com/.well-known/oauth-protected-resource/mcp/splitbill to none
- Authorization servers: https://sposched.jittee.com/split to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://jittee.com/.well-known/oauth-protected-resource/mcp/splitbill to none
- Authorization servers: https://sposched.jittee.com/split to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.0.7. Values in angle brackets are yours to fill in.
claude mcp add --transport http splitbill https://jittee.com/mcp/splitbillclaude mcp add --transport http splitbill https://jittee.com/mcp/splitbillRun 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__splitbill__list_splits",
"mcp__splitbill__get_split"
],
"ask": [
"mcp__splitbill__create_split"
],
"deny": []
}
}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 splitbill. Review it before you use it.
Capability tags behind 2 rules
- mcp__splitbill__list_splits untrusted-input
- mcp__splitbill__get_split private-data
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/com.jittee/splitbill/verify?hash=7860084c290079bff6d7786624254685e1d3d1f4dc8b594aa0f496ced4e6c93a" | jq -e '.changed == false'Pinned hash 7860084c2900, from Oct 29, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.jittee/splitbill/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.jittee/splitbill)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:57 UTC.
splitbill MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the splitbill MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 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 splitbill MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the splitbill MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the splitbill MCP server have?
- 3 tools: 1 write, 2 read. create_split, list_splits and get_split.
Does the splitbill MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the splitbill MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the splitbill MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 29, 2026.