# Zovo Group Expenses (remote · group-expenses.zovo.one)

Shared trip and house expenses

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

## Components

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

## Channel facts

- Endpoint: `https://group-expenses.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_expense_ledger).
  - 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**: 76/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 871 tokens (~174/item across 5 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Group Expenses MCP server?

Zovo Group Expenses is a hosted endpoint at https://group-expenses.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-group-expenses 'https://group-expenses.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-group-expenses:
    url: "https://group-expenses.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-group-expenses": {
      "type": "http",
      "url": "https://group-expenses.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-21 (score 73, +1)

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

### 2026-11-18 (score 72, +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 71, +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-14 (score 70, +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-11-12 (score 69, +1)

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

### 2026-11-10 (score 68, +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-11-09 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (4)

### `create_expense_ledger` (~318 tokens)

Create a shared expense ledger page

Use this when a group wants to track shared costs for a trip, a shared house or an event and split them fairly: it publishes a shared web page where everyone adds what they paid, and returns a public link to share and a private organizer link. Optional starting expenses and payments can be included. Amounts use whole minor units of one currency (no conversion). Members are first names, 2 to 30. Does not move money, convert currencies or send reminders. Do not use for a one-off bill split that nobody else needs to see.

Input parameters:

- `currency` (string, required): ISO 4217 currency code, e.g. EUR, USD, GBP, JPY, KWD.
- `expenses` (array): Optional expenses to add right away.
- `members` (array, required): First names of the people sharing costs (2-30), e.g. ["Ana", "Ben", "Chi"].
- `note` (string): Optional note shown on the page, e.g. Add every shared cost here.
- `number_format` (string): How people type amounts on the page, e.g. 1,234.56. Default depends on the currency (EUR uses 1.234,56).
- `payments` (array): Optional payments already made between members.
- `time_zone` (string): Optional IANA time zone for dates on the page, e.g. Europe/Lisbon. Default UTC.
- `title` (string): Name of the ledger, e.g. Lisbon trip 2026.

Output parameters:

- `changes` (array)
- `closed` (boolean)
- `currency` (string)
- `ended` (boolean)
- `expense_count` (number)
- `expires_at` (string)
- `manage_url` (string)
- `minor_digits` (number)
- `number_format` (string)
- `payment_count` (number)
- `people` (array)
- `people_count` (object)
- `public_url` (string)
- `recent` (array)
- `recent_count` (object)
- `rule` (string)
- `settle_up` (array)
- `settle_up_zeroes_all` (boolean)
- `title` (string)
- `total` (string)

### `show_expense_ledger_results` (~120 tokens)

Show ledger balances and settle-up

Use this when the organizer asks for the balances, who owes whom, or the settle-up payments of a shared expense ledger made with create_expense_ledger. Takes the private organizer link and returns each person's paid, share and balance, the settle-up list and recent expenses. Does not change the ledger. Do not use without the organizer link.

Input parameters:

- `manage_link` (string, required): The private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...

Output parameters:

- `changes` (array)
- `closed` (boolean)
- `currency` (string)
- `ended` (boolean)
- `expense_count` (number)
- `expires_at` (string)
- `manage_url` (string)
- `minor_digits` (number)
- `number_format` (string)
- `payment_count` (number)
- `people` (array)
- `people_count` (object)
- `public_url` (string)
- `recent` (array)
- `recent_count` (object)
- `rule` (string)
- `settle_up` (array)
- `settle_up_zeroes_all` (boolean)
- `title` (string)
- `total` (string)

### `add_ledger_expenses` (~143 tokens)

Add expenses to a ledger

Use this when the organizer tells you about expenses or payments to add to an existing shared ledger. Takes the private organizer link and up to 40 expenses or payments; returns the new balances. Names must match the members. Does not edit or delete expenses (use update_expense_ledger to delete).

Input parameters:

- `expenses` (array): Expenses to add.
- `manage_link` (string, required): The private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...
- `payments` (array): Payments made between members, e.g. Ben paid Ana back 42.25.

Output parameters:

- `changes` (array)
- `closed` (boolean)
- `currency` (string)
- `ended` (boolean)
- `expense_count` (number)
- `expires_at` (string)
- `manage_url` (string)
- `minor_digits` (number)
- `number_format` (string)
- `payment_count` (number)
- `people` (array)
- `people_count` (object)
- `public_url` (string)
- `recent` (array)
- `recent_count` (object)
- `rule` (string)
- `settle_up` (array)
- `settle_up_zeroes_all` (boolean)
- `title` (string)
- `total` (string)

### `update_expense_ledger` (~211 tokens)

Change, delete from or close a ledger

Use this when the organizer wants to add members, delete expenses by their number (#3), rename the ledger, change the note, or close or reopen the page. Takes the private organizer link. Deleting removes the expense from all balances. Does not remove members who are already in expenses.

Input parameters:

- `add_members` (array): New members to add, e.g. ["Eli"].
- `delete_expenses` (array): Numbers of expenses or payments to delete, as shown on the page, e.g. [3].
- `manage_link` (string, required): The private organizer link returned when the ledger was created, e.g. https://group-expenses.zovo.one/m/AbC.../XyZ...
- `note` (string): New note shown on the page; empty text removes it.
- `status` (string): closed stops new expenses (balances stay visible); open allows them again.
- `title` (string): New title, e.g. Lisbon trip (final).

Output parameters:

- `changes` (array)
- `closed` (boolean)
- `currency` (string)
- `ended` (boolean)
- `expense_count` (number)
- `expires_at` (string)
- `manage_url` (string)
- `minor_digits` (number)
- `number_format` (string)
- `payment_count` (number)
- `people` (array)
- `people_count` (object)
- `public_url` (string)
- `recent` (array)
- `recent_count` (object)
- `rule` (string)
- `settle_up` (array)
- `settle_up_zeroes_all` (boolean)
- `title` (string)
- `total` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 67
- 2026-11-08: 67

## Common questions

### What is the Zovo Group Expenses MCP server?

Zovo Group Expenses is an MCP server listed in the public MCP registry as io.github.theluckystrike/group-expenses. Shared trip and house expenses. This page covers its hosted endpoint (https://group-expenses.zovo.one/mcp).

### Is the Zovo Group Expenses MCP server safe to use?

Zovo Group Expenses 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 Group Expenses MCP server expose?

Zovo Group Expenses exposes 4 tools: create_expense_ledger, show_expense_ledger_results, add_ledger_expenses, update_expense_ledger. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.

### Does the Zovo Group Expenses MCP server require authentication?

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

### Is the Zovo Group Expenses MCP server still maintained?

Zovo Group Expenses 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 Group Expenses MCP server?

VerifyMCP ran 14 checks on Zovo Group Expenses, 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://group-expenses.zovo.one/mcp
- Website: https://group-expenses.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-group-expenses/group-expenses.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-group-expenses/group-expenses/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-group-expenses/group-expenses.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-group-expenses/group-expenses
