McpStamp Petty Cash MCP server
io.github.theluckystrike/petty-cashtheluckystrikestreamable-httpv0.23.0Scanned
Run a petty cash float: numbered vouchers, cash counts, over and short, replenishment amounts.
9 tools: 1 can delete or cancel things, 1 do something that can't be undone, 6 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the McpStamp Petty Cash MCP server can do
The McpStamp Petty Cash MCP server is published by the GitHub account theluckystrike. It has 9 tools. It can delete or cancel things (1 tool: voucher_delete), do things that cannot be undone, such as sending, paying or publishing (topup_record) and create or change data (6 tools: float_open, voucher_add, reconcile, replenish_request and 2 more). 1 tool only reads.
1 tool brings in text other people can write (license_status).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.23.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Deletes or cancels 1Claude Code: deny
voucher_deleteDelete a voucher entered wrongly, by its VOU number.No findings
Why it is in this group
- The name "voucher_delete" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
topup_recordRecord cash put into the tin, in whole MINOR units, with the date and source, and return the new balance against the imprest.No findings
Why it is in this group
- The name "topup_record" says "topup": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 6Claude Code: ask
float_openOpen a petty cash float on the imprest system and return its id.No findings
Why it is in this group
- The name "float_open" says "open": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
float_reportReport 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
reconcileCount 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 recon…1 finding
Why it is in this group
- The description's first verb is "count": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "reconcile" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "count": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
replenish_requestWork 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.No findings
Why it is in this group
- The name "replenish_request" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
voucher_addRecord one voucher paid out of the tin and return its VOU-YYYY-NNNN number.No findings
Why it is in this group
- The name "voucher_add" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
license_statusReport 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.Reads text others writeNo findings
Why it is in this group
- The name "license_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:34 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash
- Authorization servers
- https://mcp.zovo.one
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.zovo.one/mcp/petty-cash: tools/list returned 9 tools to an anonymous client, including voucher_delete (destructive), topup_record (irreversible), float_open (write), voucher_add (write), reconcile (write) and 3 more
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 8
- Protocol version: none to 2025-06-18
- Nov 6, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warnreconcile
The server marks "reconcile" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "count": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 8 (and 1 more).View diff
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 8
- Protocol version: none to 2025-06-18
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/petty-cash
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.23.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http petty-cash https://mcp.zovo.one/mcp/petty-cashclaude mcp add --transport http petty-cash https://mcp.zovo.one/mcp/petty-cashRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__petty-cash__license_status"
],
"ask": [
"mcp__petty-cash__float_open",
"mcp__petty-cash__topup_record",
"mcp__petty-cash__voucher_add",
"mcp__petty-cash__reconcile",
"mcp__petty-cash__replenish_request",
"mcp__petty-cash__float_report",
"mcp__petty-cash__license_activate"
],
"deny": [
"mcp__petty-cash__voucher_delete"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as petty-cash. Review it before you use it.
Capability tags behind 1 rule
- mcp__petty-cash__license_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/petty-cash/verify?hash=637217823fc4e64f346bd25590920541554da44d7c60c165b84ef097f1f5d610" | jq -e '.changed == false'Pinned hash 637217823fc4, from Nov 15, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/petty-cash/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/petty-cash)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.
McpStamp Petty Cash MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the McpStamp Petty Cash MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the McpStamp Petty Cash MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: voucher_delete.
Can the McpStamp Petty Cash MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: topup_record.
What tools does the McpStamp Petty Cash MCP server have?
- 9 tools: 1 destructive, 1 irreversible, 6 write, 1 read. voucher_delete, topup_record, float_open, voucher_add, reconcile, replenish_request, float_report, license_activate and 1 more.
Does the McpStamp Petty Cash MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the McpStamp Petty Cash MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the McpStamp Petty Cash MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.