# io.github.theluckystrike/imprest-account (mcpb · petty-cash.mcpb)

An imprest account: vouchers by category, the count, and the cheque that restores the float.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `petty-cash.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash.md), [page](https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/petty-cash.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 22/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 157 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **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 1028 tokens (~102/item across 10 items; 9 tools + 1 resources), lean.
  - 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**: 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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/petty-cash.mcpb`

## 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 54, +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-09-18 (score 53, +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-16 (score 52, +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-15 (score 51, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 48)

First indexed and scored.

## 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` (~143 tokens)

Record cash put into the float

Record cash put into the tin: the amount in whole minor units, the date and where it came from. It reimburses every voucher up to that date, which is what a replenishment cheque does. Free.

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` (~74 tokens)

Delete a voucher

Delete a voucher that was entered wrongly, by its VOU number. A voucher already covered by a reconciliation is refused: the cash it took out was counted, so removing it would make a past count wrong. Free.

Input parameters:

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

### `reconcile` (~112 tokens)

Count the tin and reconcile

Count the cash and reconcile: the expected balance, the difference to the minor unit, and every voucher since the last count, which this marks reconciled. Records the count. Free and unlimited.

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 every float: the balance against its imprest, what is unreconciled, the last count, and the history of what the counts found over or short, per float and in total. 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` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### What is the io.github.theluckystrike/imprest-account MCP server?

io.github.theluckystrike/imprest-account is an MCP server listed in the public MCP registry as io.github.theluckystrike/imprest-account. An imprest account: vouchers by category, the count, and the cheque that restores the float. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/petty-cash.mcpb).

### Is the io.github.theluckystrike/imprest-account MCP server safe to use?

io.github.theluckystrike/imprest-account scores 54 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/imprest-account MCP server expose?

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

### What licence is the io.github.theluckystrike/imprest-account MCP server under?

io.github.theluckystrike/imprest-account declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/petty-cash
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-imprest-account/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-petty-cash
