io.github.theluckystrike/petty-cash
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
A petty cash float on the imprest system: vouchers, reconciliation and the replenishment.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1145 tokens (~104/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-petty-cash 'https://mcp.zovo.one/mcp/petty-cash'
{
"mcpServers": {
"theluckystrike-petty-cash": {
"url": "https://mcp.zovo.one/mcp/petty-cash"
}
}
} {
"servers": {
"theluckystrike-petty-cash": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/petty-cash"
}
}
} [mcp_servers.theluckystrike-petty-cash] url = "https://mcp.zovo.one/mcp/petty-cash"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-petty-cash": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/petty-cash",
"enabled": true
}
}
} openclaw mcp add theluckystrike-petty-cash --url 'https://mcp.zovo.one/mcp/petty-cash' --transport streamable-http
mcp_servers:
theluckystrike-petty-cash:
url: "https://mcp.zovo.one/mcp/petty-cash" {
"McpServers": {
"theluckystrike-petty-cash": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/petty-cash"
}
}
} assistant mcp add theluckystrike-petty-cash -t streamable-http -u 'https://mcp.zovo.one/mcp/petty-cash'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 0
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 +1
- 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 security
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- 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. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/petty-cash
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/petty-cash | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/petty-cash | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/petty-cash |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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.
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.