McpStamp Petty Cash
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Run a petty cash float: numbered vouchers, cash counts, over and short, replenishment amounts.
Available components
Last scanned (22 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 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
- Context-footprint check failed: tool/resource definitions use about 1247 tokens (~113/item across 11 items; 9 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +70
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 −68
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 4 Nov 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 | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/petty-cash |
| Authorisation server | https://mcp.zovo.one |
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.
How do I install the McpStamp Petty Cash MCP server?
McpStamp 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'
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 hosted endpoint (https://mcp.zovo.one/mcp/petty-cash).
Is the McpStamp Petty Cash MCP server safe to use?
McpStamp Petty Cash scores 95 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 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,069 tokens of context every time the server is loaded.
Does the McpStamp Petty Cash MCP server require authentication?
Yes. McpStamp 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 McpStamp Petty Cash MCP server still maintained?
McpStamp Petty Cash is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.