Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/cash-float

MCPB · PETTY-CASH.MCPB

Run a cash float: record what was paid out, count the tin, and raise the top-up.

Available components

mcpb · petty-cash.mcpb 5
0 this week 5 Trust /100

Last scanned (11 hours ago)

Scores higher than 10% of MCPB servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security0
  • 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 could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Install-script risk could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Dependency health could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
Provenance & Transparency26
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. View diagnostics → Unverified
  • Licence could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Maintenance history could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • Source repository
  • Security disclosure

Checks we could not complete (12)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • Provenance in Provenance & TransparencyBuild provenance could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • License in Provenance & TransparencyLicence could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • Maintenance in Provenance & TransparencyMaintenance history could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Bundle digest

    Registry says
    785f160887ecc6a2a2eb03f5628ca41e474aab8f4a14dda4d66eb4caafdb8919
    Package shows
    The bundle hashes to a different SHA-256 (the observed digest is not recorded)

    The bundle we downloaded does not hash to the SHA-256 the registry entry declares, so we did not read it or look for an attestation. This is a fact about the published file. See the evidence →

Changelog

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.

  • 3 Nov 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 2 Nov 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 26 Oct 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 25 Oct 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 19 Oct 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 15 Oct 26 0
    • Package version: 0.21.0 → 0.22.5 functional
  • 14 Oct 26 −57
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → unverified ▼ security
    • Known CVEs: partial → unverified ▼ security
    • Provenance: fail → unverified ▼ security
    • Stability: 0.97 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Install scripts: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: 0.81 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • License: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Maintenance: pass → unverified ▼ functional
    • Licence: MIT functional
    • Package version: 0.21.0 → 0.22.5 functional
  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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.22.5

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem mcpb
Reason Bundle differs from the registry digest

Background: How many MCP packages publish verified provenance →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the io.github.theluckystrike/cash-float MCP server?

io.github.theluckystrike/cash-float 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, 785f160887ecc6a2a2eb03f5628ca41e474aab8f4a14dda4d66eb4caafdb8919; the commands to do that are on this page. If it does not match, do not open it.

mcpb · petty-cash.mcpb

Download bundle

Check 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

785f160887ecc6a2a2eb03f5628ca41e474aab8f4a14dda4d66eb4caafdb8919

macOS / Linux 

echo "785f160887ecc6a2a2eb03f5628ca41e474aab8f4a14dda4d66eb4caafdb8919  petty-cash.mcpb" | shasum -a 256 -c

Windows (PowerShell) 

(Get-FileHash -Algorithm SHA256 .\petty-cash.mcpb).Hash -eq "785f160887ecc6a2a2eb03f5628ca41e474aab8f4a14dda4d66eb4caafdb8919"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.