# Zovo Bill Splitter (remote · bill-splitter.zovo.one)

Split the bill without the awkward math.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `bill-splitter.zovo.one`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter.md), [page](https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter)

## Channel facts

- Endpoint: `https://bill-splitter.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1576 tokens (~394/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Bill Splitter MCP server?

Zovo Bill Splitter is a hosted endpoint at https://bill-splitter.zovo.one/mcp, 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 theluckystrike-bill-splitter 'https://bill-splitter.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-bill-splitter": {
      "url": "https://bill-splitter.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-bill-splitter": {
      "type": "http",
      "url": "https://bill-splitter.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-bill-splitter]
url = "https://bill-splitter.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-bill-splitter": {
      "type": "remote",
      "url": "https://bill-splitter.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-bill-splitter --url 'https://bill-splitter.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-bill-splitter:
    url: "https://bill-splitter.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-bill-splitter": {
      "Transport": "http",
      "Url": "https://bill-splitter.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-bill-splitter -t streamable-http -u 'https://bill-splitter.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-bill-splitter": {
      "type": "http",
      "url": "https://bill-splitter.zovo.one/mcp"
    }
  }
}
```

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-10-23 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 73)

First indexed and scored.

## MCP tools (3)

### `split_bill` (~781 tokens)

Split a bill

Use this when the user wants to split a restaurant bill, check, receipt, takeout order, or any single bill between people: evenly or item by item (who had what), with tax, tip, service charge, coupons, delivery fees, or rounding up. Tax, tip, and service charge are shared in proportion to each person's pre-tax subtotal; every share is exact to the cent and the shares add up exactly to the total (largest-remainder rounding). Optional paid_by lists who owes the payer. Does not read receipt photos (pass the items as text), handle several payers or many bills (use settle_group_expenses), or convert currencies.

Input parameters:

- `bill_amount` (number): Use instead of items to split one amount evenly, e.g. 120. It is the amount before any tax_percent or tip_percent you add here; if the bill already includes tax, leave tax out.
- `currency` (string): ISO 4217 code, e.g. USD, EUR, GBP, JPY. Defaults to USD. JPY has no decimals, KWD has three.
- `discount_amount` (number): Coupon or deal on the whole bill in money, applied before tax, e.g. 15.
- `discount_percent` (number): Coupon or deal on the whole bill in percent, applied before tax, e.g. 10.
- `equal_fee_amount` (number): A flat fee split equally rather than by what people ordered, e.g. a 6.99 delivery fee or a cover charge.
- `items` (array): Line items from the receipt with who shared each one. Example: [{"description": "Pizza", "price": 24, "shared_by": ["Ana", "Ben"]}, {"description": "Salad", "price": 12, "shared_by": ["Chloe"]}]. Omi…
- `paid_by` (string): Who paid the whole bill, e.g. "Ana". Adds a list of who owes them how much.
- `people` (array): Everyone splitting the bill, e.g. ["Ana", "Ben", "Chloe"]. Needed when some items are shared by everyone or when someone had nothing. Optional if every item lists shared_by.
- `people_count` (integer): Number of people when names are not given, e.g. 5. They are labelled Person 1 to Person 5.
- `round_up_to` (number): Round each person's share up to a multiple of this amount, e.g. 1 for whole dollars or 5. The extra is shown separately.
- `service_charge_amount` (number): Service charge in money, e.g. 9.75.
- `service_charge_percent` (number): Service charge rate added by the restaurant, e.g. 12.5. Shared in proportion to each person's subtotal.
- `tax_amount` (number): Tax in money exactly as printed on the receipt, e.g. 7.38. Shared in proportion to each person's subtotal.
- `tax_percent` (number): Sales tax or VAT rate added on top of the item subtotal (after any discount), e.g. 8.875. Use tax_amount instead when the receipt shows the tax in money.
- `tip_amount` (number): Tip in money, e.g. 25. Shared in proportion to each person's subtotal.
- `tip_base` (string): What tip_percent applies to: pre_tax (default, subtotal after discounts) or post_tax (subtotal plus service charge plus tax).
- `tip_percent` (number): Tip rate, e.g. 18 or 20. Calculated on the pre-tax subtotal unless tip_base is post_tax.
- `title` (string): Optional label, e.g. "Dinner at Luigi's".

Output parameters:

- `check` (object)
- `currency` (string)
- `display` (object)
- `hints` (array)
- `items` (array)
- `kind` (string)
- `labels` (object)
- `minor_units` (number)
- `owes` (array)
- `paid_by` (string|null)
- `people` (array)
- `settings` (object)
- `title` (string)
- `totals` (object)
- `warnings` (array)

### `settle_group_expenses` (~330 tokens)

Settle group expenses

Use this when a group (trip, vacation, roommates, couple, event) has several shared expenses paid by different people and wants to know who owes who and how to settle up. Each expense can be split equally, by exact amounts, by percentages, or by shares. Returns each person's balance (paid minus share, summing to exactly zero) and the fewest payments that settle every balance to the cent, plus a CSV of payments, balances, and expenses. One currency per call: mixed currencies are rejected and nothing is converted. Does not send payment requests, move money, or remember the group; for one restaurant bill use split_bill.

Input parameters:

- `currency` (string): ISO 4217 code for every expense, e.g. USD, EUR, GBP. Defaults to USD. Mixed currencies are rejected; nothing is converted.
- `expenses` (array, required): Every shared expense. Example: [{"description": "Airbnb", "amount": 360, "paid_by": "Ana"}, {"description": "Gas", "amount": 90, "paid_by": "Ben", "split_among": ["Ben", "Chloe"]}]. Record a repaymen…
- `people` (array): Everyone in the group, e.g. ["Ana", "Ben", "Chloe", "Dev"]. Needed when "everyone" should include someone who never paid. Optional otherwise.
- `title` (string): Optional label, e.g. "Lisbon trip".

Output parameters:

- `currency` (string)
- `display` (object)
- `downloads` (object)
- `expense_count` (number)
- `expenses` (array)
- `expenses_shown` (number)
- `hints` (array)
- `kind` (string)
- `minimal` (boolean)
- `minor_units` (number)
- `nonzero_balances` (number)
- `people` (array)
- `title` (string)
- `totals` (object)
- `transfer_count` (number)
- `transfers` (array)
- `warnings` (array)

### `split_rent` (~364 tokens)

Split rent

Use this when roommates or housemates want to split rent fairly: by bedroom size (square feet or metres) with a shared-space portion split per occupant, by income, or equally, with optional per-room adjustments (private bathroom, no window), couples sharing a room, and utilities split per occupant. Every amount is exact to the cent and the parts add up exactly to the rent. Does not give legal or tenancy advice, collect rent, or handle one-off shared expenses (use settle_group_expenses for those).

Input parameters:

- `basis` (string): How to split: room_size (default when every room has a size), income (in proportion to income), or equal (per occupant).
- `currency` (string): ISO 4217 code, e.g. USD, EUR, GBP. Defaults to USD.
- `extra_costs` (number): Other monthly costs split equally per occupant, e.g. 180 for utilities and internet.
- `rooms` (array, required): Each bedroom or person. Example: [{"name": "Ana", "size": 160}, {"name": "Ben", "size": 120}, {"name": "Chloe", "size": 100}].
- `shared_area` (number): Area of shared space (kitchen, living room, shared bathroom) in the same unit as the room sizes, e.g. 400. Its share of the total area is split equally per occupant.
- `shared_percent` (number): Alternative to shared_area: percent of the rent treated as shared space and split equally per occupant, e.g. 40. Defaults to 50 for room_size when shared_area is not given.
- `total_rent` (number, required): Total monthly rent for the home, e.g. 3200.

Output parameters:

- `assumptions` (array)
- `basis` (string)
- `currency` (string)
- `display` (object)
- `hints` (array)
- `kind` (string)
- `minor_units` (number)
- `rooms` (array)
- `settings` (object)
- `shared_percent` (string|null)
- `shared_source` (string|null)
- `totals` (object)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter#diagnostics

## Score history

- 2026-10-23: 73
- 2026-10-22: 73

## Common questions

### What is the Zovo Bill Splitter MCP server?

Zovo Bill Splitter is an MCP server listed in the public MCP registry as io.github.theluckystrike/bill-splitter. Split the bill without the awkward math. This page covers its hosted endpoint (https://bill-splitter.zovo.one/mcp).

### Is the Zovo Bill Splitter MCP server safe to use?

Zovo Bill Splitter scores 73 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 Zovo Bill Splitter MCP server expose?

Zovo Bill Splitter exposes 3 tools: split_bill, settle_group_expenses, split_rent. Their descriptions and schemas cost roughly 1,475 tokens of context every time the server is loaded.

### Does the Zovo Bill Splitter MCP server require authentication?

No. We connected to Zovo Bill Splitter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Bill Splitter MCP server still maintained?

Zovo Bill Splitter is still listed as active in the MCP registry. We last reached this channel on 23 October 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://bill-splitter.zovo.one/mcp
- Website: https://bill-splitter.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-bill-splitter/bill-splitter