# Zovo Tip Pool Calculator (remote · tip-pool.zovo.one)

A tip pool calculator and tip out calculator for restaurant, bar, cafe and salon staff.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://tip-pool.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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 68/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 1464 tokens (~488/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 2 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**: 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 Tip Pool Calculator MCP server?

Zovo Tip Pool Calculator is a hosted endpoint at https://tip-pool.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-tip-pool 'https://tip-pool.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-tip-pool:
    url: "https://tip-pool.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-tip-pool": {
      "type": "http",
      "url": "https://tip-pool.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-11-20 (score 78, +1)

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

### 2026-11-18 (score 77, +1)

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

### 2026-11-16 (score 76, +1)

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

### 2026-11-13 (score 75, +1)

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

### 2026-11-11 (score 74, +1)

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

### 2026-11-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (2)

### `calculate_tip_pool` (~827 tokens)

Calculate tip pool

Use this when the user wants a tip pool calculator: split pooled tips among restaurant, bar, cafe or salon staff by hours worked (how to split tips by hours), by points x hours, by role percentage (e.g. 70% servers, 20% bussers, 10% bar, then by hours inside each role), or equally. Accepts cash and card tips with an optional card fee percent, a staff list as objects or pasted text/CSV, and an optional week view (shift_tips plus a shift on each staff row). Returns each person's share in cents with largest-remainder rounding so shares add up to the pool, the per-hour rate, an explanation, warnings (e.g. a manager in the pool), and a printable PDF tip sheet with signature lines plus a CSV. Does not give legal advice, decide who may be in a pool, compute wages or taxes, or connect to a POS. Do not use for splitting a restaurant bill among diners.

Input parameters:

- `card_fee_percent` (number|string|null): Card processing fee percent to deduct from card tips before splitting, e.g. 2.9. Default none.
- `card_tips` (number|string|null): Credit card tips, e.g. 820.50. Optional; the card fee applies to these.
- `cash_tips` (number|string|null): Cash tips, e.g. 420. Optional.
- `currency` (string|null): ISO currency code, default USD, e.g. EUR, GBP, CAD.
- `label` (string|null): Optional title for the tip sheet, e.g. "Friday dinner, Oct 23" or "Week of Oct 19".
- `method` (string|null): How to split: "hours" (by hours worked), "points" (points x hours), "role_percent" (fixed percent per role, e.g. 70/20/10, then by hours inside each role), or "equal". Default: chosen from the data (…
- `role_percentages`: Percent of the pool per role for method role_percent, e.g. {"server":70,"busser":20,"bartender":10} or "servers 70%, bussers 20%, bar 10%".
- `role_points`: Points per role for the points method when people have no points of their own, e.g. {"server":10,"bartender":8,"busser":5}.
- `round_to` (string|null): "cent" (default) or "dollar" to pay whole dollars in cash; any coins left over are reported, not assigned.
- `shift_tips`: Week view: tips per shift, with each staff row's shift set, e.g. {"Mon":420,"Tue":385.5} or "Mon 420, Tue 385.50". Each shift is split on its own, then totals are added per person.
- `shifts`: Alternative week view: one item per shift with its own tips and staff, e.g. [{"label":"Fri","total_tips":600,"staff":"Ana 5, Ben 5"},{"label":"Sat","total_tips":900,"staff":"Ana 6, Cara 6"}].
- `staff`: Everyone sharing the pool. Array of {name, role, hours, points, shift}, or one pasted block (one person per line, CSV with a header row is fine), e.g. [{"name":"Ana","role":"server","hours":6.5},{"na…
- `total_tips` (number|string|null): Total tips to split (cash plus card), e.g. 1240.50 or "$1,240.50". Leave out when cash_tips and card_tips are given, or when shift_tips is used.

Output parameters:

- `assumptions` (array)
- `currency` (string)
- `downloads` (object)
- `explanation` (string)
- `label` (string)
- `method` (string)
- `method_label` (string)
- `note` (string)
- `people` (array)
- `pool` (object)
- `roles` (array)
- `shifts` (array)
- `warnings` (array)

### `calculate_tip_out` (~475 tokens)

Calculate tip-out

Use this when the user wants a tip out calculator: servers or bartenders tip out a percent of their sales or tips to support staff (bussers, bartenders, hosts, food runners, barbacks). Takes each server's sales and/or tips and the tip-out rules (e.g. busser 3% of sales, bar 1.5% of sales), plus optional support staff with roles and hours. Returns each server's tip-out per role (rounded to the cent), what each server keeps, each support person's share by hours with largest-remainder rounding so it adds up to what was tipped out, warnings, and a printable PDF tip-out sheet with signature lines plus a CSV. Does not give legal advice, compute wages or taxes, or connect to a POS. Do not use for a shared pool split by hours (use calculate_tip_pool) or for a bill split among diners.

Input parameters:

- `currency` (string|null): ISO currency code, default USD, e.g. EUR.
- `label` (string|null): Optional title for the tip-out sheet, e.g. "Saturday dinner".
- `servers` (required): Servers or bartenders who tip out, each with sales and/or tips. Array of {name, sales, tips}, or pasted lines, e.g. [{"name":"Ana","sales":1850,"tips":340}] or "Ana sales 1850 tips 340\nBen sales 142…
- `support_staff`: Optional people receiving the tip-out, with role and hours, e.g. [{"name":"Kim","role":"busser","hours":6}]. Each role's tip-out is split among its people by hours (equal if no hours).
- `tip_out_basis` (string|null): "sales" or "tips": what a percent without "of sales" or "of tips" is taken from. Default: sales when every server has sales, else tips.
- `tip_outs` (required): Who gets what share, e.g. "busser 3% of sales, bartender 1.5% of sales, host 1% of sales" or [{"role":"busser","percent":3,"basis":"sales"}]. A plain 3 or "3%" means 3% to the support staff as one gr…

Output parameters:

- `assumptions` (array)
- `currency` (string)
- `downloads` (object)
- `explanation` (string)
- `label` (string)
- `note` (string)
- `servers` (array)
- `support_staff` (array)
- `tip_outs` (array)
- `totals` (object)
- `unassigned` (array)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72

## Common questions

### What is the Zovo Tip Pool Calculator MCP server?

Zovo Tip Pool Calculator is an MCP server listed in the public MCP registry as io.github.theluckystrike/tip-pool. A tip pool calculator and tip out calculator for restaurant, bar, cafe and salon staff. This page covers its hosted endpoint (https://tip-pool.zovo.one/mcp).

### Is the Zovo Tip Pool Calculator MCP server safe to use?

Zovo Tip Pool Calculator scores 78 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 Tip Pool Calculator MCP server expose?

Zovo Tip Pool Calculator exposes 2 tools: calculate_tip_pool, calculate_tip_out. Their descriptions and schemas cost roughly 1,302 tokens of context every time the server is loaded.

### Does the Zovo Tip Pool Calculator MCP server require authentication?

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

### Is the Zovo Tip Pool Calculator MCP server still maintained?

Zovo Tip Pool Calculator is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo Tip Pool Calculator MCP server?

VerifyMCP ran 14 checks on Zovo Tip Pool Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tip-pool.zovo.one/mcp
- Website: https://tip-pool.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-tip-pool/tip-pool.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-tip-pool/tip-pool/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-tip-pool/tip-pool.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-tip-pool/tip-pool
