com.jittee/splitbill
REMOTE · JITTEE.COM · 2 COMPONENTS · SCANNED SEP 24
Split bills and collect payments through PayNow (Singapore) from your AI. MCP server for SplitBill.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · jittee.com
claude mcp add --transport http com-jittee-splitbill 'https://jittee.com/mcp/splitbill'
{
"mcpServers": {
"com-jittee-splitbill": {
"url": "https://jittee.com/mcp/splitbill"
}
}
} {
"servers": {
"com-jittee-splitbill": {
"type": "http",
"url": "https://jittee.com/mcp/splitbill"
}
}
} [mcp_servers.com-jittee-splitbill] url = "https://jittee.com/mcp/splitbill"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jittee-splitbill": {
"type": "remote",
"url": "https://jittee.com/mcp/splitbill",
"enabled": true
}
}
} openclaw mcp add com-jittee-splitbill --url 'https://jittee.com/mcp/splitbill' --transport streamable-http
mcp_servers:
com-jittee-splitbill:
url: "https://jittee.com/mcp/splitbill" {
"McpServers": {
"com-jittee-splitbill": {
"Transport": "http",
"Url": "https://jittee.com/mcp/splitbill"
}
}
} assistant mcp add com-jittee-splitbill -t streamable-http -u 'https://jittee.com/mcp/splitbill'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +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.
- 23 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 20 Sept 26 +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.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://jittee.com/mcp/splitbill
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jittee.com | CN=WR3,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | RSA 2048 | SHA256-RSA | fa167bdece0003d4124f1d0157c8da49 |
| SANs: jittee.com, *.jittee.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jittee.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jittee.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://jittee.com/mcp/splitbill/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://jittee.com/mcp/splitbill/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://jittee.com/mcp/splitbill/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://jittee.com/mcp/splitbill |
| Authorisation server | https://sposched.jittee.com/split |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jittee.com/mcp/splitbill | Verified | 200 | |
| http (plaintext) | http://jittee.com/mcp/splitbill | HTTPS enforced | 301 | https://jittee.com:443/mcp/splitbill |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_split Create a split bill ~368
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| manage_url | string | yes | Manage URL. FOR THE ORGANISER ONLY — it can change the split. |
| next_step | string | yes | What to do next. |
| paynow | object | yes | Who collects the money (saved with this connection). |
| people | number | yes | How many share the bill, including whoever paid up front. |
| share_urls | array | yes | Share URLs — one per amount. |
| status_url | string|null | – | Read-only URL. Safe to share. |
| summary | string | yes | A one-line summary to read out (how much each, how many people). |
| total | number | yes | The total. |
| warnings | array | – | Anything worth mentioning about rounding or head count. |
No examples provided.
get_split Check how a split is going ~55
Return one split in full: who owes what, whether they have paid, the notes they left, and the share URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | The t= value from the manage URL, or the whole manage URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| collected | number | yes | How much has come in. |
| members | array | yes | – |
| paynow | object | yes | – |
| people | number | yes | – |
| share_urls | array | yes | – |
| status_url | string|null | – | – |
| title | string | yes | – |
| total | number | yes | – |
No examples provided.
list_splits List the splits made with this connection ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many to return (default 10, max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| splits | array | yes | Newest first. |
No examples provided.
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.