# io.github.theluckystrike/petty-cash (remote · mcp.zovo.one)

A petty cash float on the imprest system: vouchers, reconciliation and the replenishment.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-petty-cash/mcp-petty-cash.md), [page](https://verifymcp.io/servers/theluckystrike-petty-cash/mcp-petty-cash)
- mcpb · `petty-cash.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-petty-cash/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-petty-cash.md), [page](https://verifymcp.io/servers/theluckystrike-petty-cash/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-petty-cash)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/petty-cash`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.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-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1145 tokens (~104/item across 11 items; 9 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "voucher_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 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.

## Install

### How do I install the io.github.theluckystrike/petty-cash MCP server?

io.github.theluckystrike/petty-cash is a hosted endpoint at https://mcp.zovo.one/mcp/petty-cash, 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-petty-cash 'https://mcp.zovo.one/mcp/petty-cash'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-petty-cash:
    url: "https://mcp.zovo.one/mcp/petty-cash"
```

### Netclaw

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

### Vellum

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

### Other

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

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-09-20 (score 83, +1)

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

### 2026-09-18 (score 82, +1)

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

### 2026-09-17 (score 81, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 81, +1)

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

### 2026-09-13 (score 80, +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-09-11 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, +1)

- [security] Tool “voucher_delete” rewrote its description, which is the text the model reads
- [security] Tool “float_report” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “reconcile” rewrote its description, which is the text the model reads
- [security] Tool “topup_record” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 96
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass

## MCP tools (9)

### `float_open` (~164 tokens)

Open a petty cash float

Open a petty cash float on the imprest system and return its id. The imprest is the cash the tin is topped back up to at every replenishment, in whole minor units. Free tier: one float.

Input parameters:

- `currency` (string, required): ISO code the cash is held in
- `custodian` (string): Who holds the tin. Defaults to the shared business profile's name
- `imprest_minor` (integer, required): The float amount in whole minor units (integer cents). 50000 is EUR 500.00
- `name` (string, required): What this tin is, e.g. Office float or Warehouse float
- `note` (string)
- `opened` (string): The date the float was handed over, YYYY-MM-DD. Default today

### `topup_record` (~146 tokens)

Record cash put into the float

Record cash put into the tin, in whole MINOR units, with the date and source, and return the new balance against the imprest. It also reimburses every voucher up to that date, as a replenishment does.

Input parameters:

- `amount_minor` (integer, required): Cash added, in whole minor units
- `date` (string, required): The date the cash went in, YYYY-MM-DD
- `float` (string): The float id, e.g. FLOAT-2026-0001, or its name. Omit when there is only one
- `source` (string, required): Where it came from, e.g. Cheque 0142, Bank withdrawal, or Owner

### `voucher_add` (~239 tokens)

Record a petty cash voucher

Record one voucher paid out of the tin and return its VOU-YYYY-NNNN number. More than the float holds is refused, and so is a byte-identical duplicate. Free tier: 20 vouchers a calendar month.

Input parameters:

- `amount_minor` (integer, required): What was paid out, in whole minor units. 1250 is EUR 12.50
- `category` (string, required): What kind of spend, e.g. postage, travel, office. It becomes the expenses:<category> account
- `date` (string, required): The date the cash left the tin, YYYY-MM-DD
- `description` (string, required): What was bought, e.g. Printer paper x5
- `duplicate_ok` (boolean): Record it even though an identical voucher exists, for a genuinely repeated purchase. Default false
- `float` (string): The float id, e.g. FLOAT-2026-0001, or its name. Omit when there is only one
- `paid_to` (string, required): Who was paid, e.g. Corner Shop
- `receipt_ref` (string): The receipt number or where the paper is filed

### `voucher_delete` (~67 tokens)

Delete a voucher

Delete a voucher entered wrongly, by its VOU number. One already covered by a reconciliation is refused, naming the count it would falsify: record a correcting voucher instead. Free.

Input parameters:

- `voucher` (string, required): The voucher id, e.g. VOU-2026-0003

### `reconcile` (~115 tokens)

Count the tin and reconcile

Count the tin: give the cash counted in whole MINOR units and the date, and get the expected balance, the difference, and every voucher since the last count, which this marks reconciled. Free.

Input parameters:

- `counted_minor` (integer, required): The cash actually counted, in whole minor units
- `date` (string, required): The date it was counted, YYYY-MM-DD
- `float` (string): The float id, e.g. FLOAT-2026-0001, or its name. Omit when there is only one

### `replenish_request` (~103 tokens)

Request a replenishment

Work out what puts the float back to its imprest: the amount, the vouchers it reimburses, the totals per category as an expense_add-ready payload, and the double entry. Writes nothing. Pro.

Input parameters:

- `date` (string): The date the request is made, YYYY-MM-DD. Default today
- `float` (string): The float id, e.g. FLOAT-2026-0001, or its name. Omit when there is only one

### `float_report` (~104 tokens)

Report the state of the float

Report each float: balance against imprest, what it takes to restore it, unreconciled vouchers with their total, the last count, and the history of what counts found over or short. Pro.

Input parameters:

- `float` (string): The float id, e.g. FLOAT-2026-0001, or its name. Omit when there is only one
- `limit` (integer): Maximum unreconciled vouchers listed per float, default and ceiling 2000

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

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

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36

## Common questions

### What is the io.github.theluckystrike/petty-cash MCP server?

io.github.theluckystrike/petty-cash is an MCP server listed in the public MCP registry as io.github.theluckystrike/petty-cash. A petty cash float on the imprest system: vouchers, reconciliation and the replenishment. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/petty-cash).

### Is the io.github.theluckystrike/petty-cash MCP server safe to use?

io.github.theluckystrike/petty-cash scores 83 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 io.github.theluckystrike/petty-cash MCP server expose?

io.github.theluckystrike/petty-cash exposes 9 tools: float_open, topup_record, voucher_add, voucher_delete, reconcile, and 4 more. Their descriptions and schemas cost roughly 1,069 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/petty-cash MCP server require authentication?

Yes. io.github.theluckystrike/petty-cash 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 io.github.theluckystrike/petty-cash MCP server still maintained?

io.github.theluckystrike/petty-cash is still listed as active in the MCP registry. We last reached this channel on 20 September 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://mcp.zovo.one/mcp/petty-cash
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/petty-cash
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-petty-cash/mcp-petty-cash.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-petty-cash/mcp-petty-cash.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-petty-cash/mcp-petty-cash