McpStamp Petty Cash
MCPB · PETTY-CASH.MCPB · 2 COMPONENTS
Run a petty cash float: numbered vouchers, cash counts, over and short, replenishment amounts.
Available components
Last scanned (1 hour ago)
Scores higher than 96% of MCPB servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 57 of 153 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1087 tokens (~108/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 10 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
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.
- 4 Nov 26 +1
- Maintenance: unverified → pass ▲ functional
- 3 Nov 26 0
- Provenance: unverified → fail ▼ security
- 2 Nov 26 +56
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.81 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.21.0 functional
- 31 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 27 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 25 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 23 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 21 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/petty-cash.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 2 |
| Stale | 57 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
float_open Open a petty cash float ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | ISO code the cash is held in |
| custodian | string | – | Who holds the tin. Defaults to the shared business profile's name |
| imprest_minor | integer | yes | The float amount in whole minor units (integer cents). 50000 is EUR 500.00 |
| name | string | yes | 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 |
No output schema declared.
No examples provided.
float_report Report the state of the float ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reconcile Count the tin and reconcile ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| counted_minor | integer | yes | The cash actually counted, in whole minor units |
| date | string | yes | 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 |
No output schema declared.
No examples provided.
replenish_request Request a replenishment ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
topup_record Record cash put into the float ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | Cash added, in whole minor units |
| date | string | yes | 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 | yes | Where it came from, e.g. Cheque 0142, Bank withdrawal, or Owner |
No output schema declared.
No examples provided.
voucher_add Record a petty cash voucher ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | What was paid out, in whole minor units. 1250 is EUR 12.50 |
| category | string | yes | What kind of spend, e.g. postage, travel, office. It becomes the expenses:<category> account |
| date | string | yes | The date the cash left the tin, YYYY-MM-DD |
| description | string | yes | 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 | yes | Who was paid, e.g. Corner Shop |
| receipt_ref | string | – | The receipt number or where the paper is filed |
No output schema declared.
No examples provided.
voucher_delete Delete a voucher ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| voucher | string | yes | The voucher id, e.g. VOU-2026-0003 |
No output schema declared.
No examples provided.
How do I install the McpStamp Petty Cash MCP server?
McpStamp Petty Cash ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 00871be7f170d6b550dfa6369a5ee8179a8d53d6d32328b5d747b013640f4d5b; the commands to do that are on this page. If it does not match, do not open it.
mcpb · petty-cash.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
00871be7f170d6b550dfa6369a5ee8179a8d53d6d32328b5d747b013640f4d5b
macOS / Linux
echo "00871be7f170d6b550dfa6369a5ee8179a8d53d6d32328b5d747b013640f4d5b petty-cash.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\petty-cash.mcpb).Hash -eq "00871be7f170d6b550dfa6369a5ee8179a8d53d6d32328b5d747b013640f4d5b"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Petty Cash MCP server?
McpStamp Petty Cash is an MCP server listed in the public MCP registry as io.github.theluckystrike/petty-cash. Run a petty cash float: numbered vouchers, cash counts, over and short, replenishment amounts. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/petty-cash.mcpb).
Is the McpStamp Petty Cash MCP server safe to use?
McpStamp Petty Cash scores 62 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 McpStamp Petty Cash MCP server expose?
McpStamp Petty Cash exposes 9 tools: float_open, topup_record, voucher_add, voucher_delete, reconcile, and 4 more. Their descriptions and schemas cost roughly 1,063 tokens of context every time the server is loaded.
What licence is the McpStamp Petty Cash MCP server under?
McpStamp Petty Cash declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.