# com.jittee/splitbill (remote · jittee.com)

Split bills and collect payments through PayNow (Singapore) from your AI. MCP server for SplitBill.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `jittee.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill.md), [page](https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill)
- npm · `splitbill-mcp`: 39/100, [markdown](https://verifymcp.io/servers/com-jittee-splitbill/splitbill-mcp.md), [page](https://verifymcp.io/servers/com-jittee-splitbill/splitbill-mcp)

## Channel facts

- Endpoint: `https://jittee.com/mcp/splitbill`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.7`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 596 tokens (~198/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.jittee/splitbill MCP server?

com.jittee/splitbill is a hosted endpoint at https://jittee.com/mcp/splitbill, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-jittee-splitbill 'https://jittee.com/mcp/splitbill'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jittee-splitbill": {
      "url": "https://jittee.com/mcp/splitbill"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jittee-splitbill": {
      "type": "http",
      "url": "https://jittee.com/mcp/splitbill"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-jittee-splitbill]
url = "https://jittee.com/mcp/splitbill"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jittee-splitbill": {
      "type": "remote",
      "url": "https://jittee.com/mcp/splitbill",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jittee-splitbill --url 'https://jittee.com/mcp/splitbill' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jittee-splitbill:
    url: "https://jittee.com/mcp/splitbill"
```

### Netclaw

```json
{
  "McpServers": {
    "com-jittee-splitbill": {
      "Transport": "http",
      "Url": "https://jittee.com/mcp/splitbill"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jittee-splitbill -t streamable-http -u 'https://jittee.com/mcp/splitbill'
```

### Other

```json
{
  "mcpServers": {
    "com-jittee-splitbill": {
      "type": "http",
      "url": "https://jittee.com/mcp/splitbill"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-23 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Schema quality: excellent → good

### 2026-09-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 75)

First indexed and scored.

## MCP tools (3)

### `create_split` (~368 tokens)

Create a split bill

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). 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.

Input parameters:

- `custom` (array): Charge one person a different amount (e.g. someone who did not drink). The rest is re-split automatically.
- `i_paid` (boolean): Did the user pay up front? (default: true) They count towards the head count but are not billed.
- `items` (array): Receipt lines. Their sum becomes the total. Payers can see them.
- `my_name` (string): What to call the user in the list (default: Me).
- `names` (array): Names of the others (only the ones you know). Empty slots get filled in by the payers themselves.
- `note` (string): A short note shown to the payers.
- `people` (number): How many people share the bill, INCLUDING the user who paid up front.
- `rounding` (string): Rounding. ceil-all = round everyone up to whole dollars and let the user absorb the difference; one-extra = split exactly and let one person carry the remainder.
- `title` (string): What the bill was for (e.g. Friday dinner). Defaults to the date and time.
- `total` (number): The total. If items are given, their sum wins.

Output parameters:

- `manage_url` (string): Manage URL. FOR THE ORGANISER ONLY — it can change the split.
- `next_step` (string): What to do next.
- `paynow` (object): Who collects the money (saved with this connection).
- `people` (number): How many share the bill, including whoever paid up front.
- `share_urls` (array): Share URLs — one per amount.
- `status_url` (string|null): Read-only URL. Safe to share.
- `summary` (string): A one-line summary to read out (how much each, how many people).
- `total` (number): The total.
- `warnings` (array): Anything worth mentioning about rounding or head count.

### `list_splits` (~75 tokens)

List the splits made with this connection

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.

Input parameters:

- `limit` (number): How many to return (default 10, max 50).

Output parameters:

- `note` (string)
- `splits` (array): Newest first.

### `get_split` (~55 tokens)

Check how a split is going

Return one split in full: who owes what, whether they have paid, the notes they left, and the share URLs.

Input parameters:

- `admin_token` (string, required): The t= value from the manage URL, or the whole manage URL.

Output parameters:

- `collected` (number): How much has come in.
- `members` (array)
- `paynow` (object)
- `people` (number)
- `share_urls` (array)
- `status_url` (string|null)
- `title` (string)
- `total` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75

## Common questions

### What is the com.jittee/splitbill MCP server?

com.jittee/splitbill is an MCP server listed in the public MCP registry as com.jittee/splitbill. Split bills and collect payments through PayNow (Singapore) from your AI. MCP server for SplitBill. This page covers its hosted endpoint (https://jittee.com/mcp/splitbill).

### Is the com.jittee/splitbill MCP server safe to use?

com.jittee/splitbill scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.jittee/splitbill MCP server expose?

com.jittee/splitbill exposes 3 tools: create_split, list_splits, get_split. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

### Does the com.jittee/splitbill MCP server require authentication?

Yes. com.jittee/splitbill asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the com.jittee/splitbill MCP server still maintained?

com.jittee/splitbill is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://jittee.com/mcp/splitbill
- Repository: https://github.com/JojoYay/splitbill-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill.json
- HTML version of this page: https://verifymcp.io/servers/com-jittee-splitbill/mcp-splitbill