Zovo Bill Splitter
REMOTE · BILL-SPLITTER.ZOVO.ONE
Split the bill without the awkward math.
Available components
Last scanned (6 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
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 23 Oct 2026 · Probed https://bill-splitter.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a4b234b128a0256013af2e38ae7a397a |
| SANs: zovo.one, bill-splitter.zovo.one, *.bill-splitter.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bill-splitter.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bill-splitter.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://bill-splitter.zovo.one/mcp | HTTPS enforced | 301 | https://bill-splitter.zovo.one/mcp |
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 →
settle_group_expenses Settle group expenses ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| display | object | yes | – |
| downloads | object | yes | – |
| expense_count | number | yes | – |
| expenses | array | yes | – |
| expenses_shown | number | yes | – |
| hints | array | yes | – |
| kind | string | yes | – |
| minimal | boolean | yes | – |
| minor_units | number | yes | – |
| nonzero_balances | number | yes | – |
| people | array | yes | – |
| title | string | yes | – |
| totals | object | yes | – |
| transfer_count | number | yes | – |
| transfers | array | yes | – |
| warnings | array | yes | – |
No examples provided.
split_bill Split a bill ~781
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| check | object | yes | – |
| currency | string | yes | – |
| display | object | yes | – |
| hints | array | yes | – |
| items | array | yes | – |
| kind | string | yes | – |
| labels | object | yes | – |
| minor_units | number | yes | – |
| owes | array | yes | – |
| paid_by | string|null | yes | – |
| people | array | yes | – |
| settings | object | yes | – |
| title | string | yes | – |
| totals | object | yes | – |
| warnings | array | yes | – |
No examples provided.
split_rent Split rent ~364
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Total monthly rent for the home, e.g. 3200. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| basis | string | yes | – |
| currency | string | yes | – |
| display | object | yes | – |
| hints | array | yes | – |
| kind | string | yes | – |
| minor_units | number | yes | – |
| rooms | array | yes | – |
| settings | object | yes | – |
| shared_percent | string|null | yes | – |
| shared_source | string|null | yes | – |
| totals | object | yes | – |
| warnings | array | yes | – |
No examples provided.
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.
remote · bill-splitter.zovo.one
claude mcp add --transport http theluckystrike-bill-splitter 'https://bill-splitter.zovo.one/mcp'
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.