io.github.theluckystrike/receipts
MCPB · RECEIPTS.MCPB
Parse raw receipt lines into itemized totals with tax. All data is local.
Available components
Last scanned (15 hours ago)
Scores higher than 90% 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 88 of 88 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 32 of 88 dependencies flagged as unhealthy. 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 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 53 tokens (~53/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 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.
- 15 Oct 26 +36
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.60 ▲ functional
- 13 Oct 26 0
- Package version: 0.22.0 → 1.0.2 functional
- 10 Oct 26 −27
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.22.0 → 1.0.2 functional
- 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
- 27 Sept 26 43
First indexed and scored.
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 18 Oct 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/receipts.mcpb@1.0.2
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 88 packages
| Packages resolved | 88 |
|---|---|
| Stale | 32 |
| 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 →
receipt_parse ~53
Parse raw receipt lines ("2 x Coffee 4.50") into an itemized total with tax.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | – |
| tax_rate | number | – | Percent, e.g. 8.5 |
No output schema declared.
No examples provided.
How do I install the io.github.theluckystrike/receipts MCP server?
io.github.theluckystrike/receipts 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, b0c375e9eb7020ba1ec47e19b5684a9e87f339ae87870f4173a34f83d88ea5cc; the commands to do that are on this page. If it does not match, do not open it.
mcpb · receipts.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
b0c375e9eb7020ba1ec47e19b5684a9e87f339ae87870f4173a34f83d88ea5cc
macOS / Linux
echo "b0c375e9eb7020ba1ec47e19b5684a9e87f339ae87870f4173a34f83d88ea5cc receipts.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\receipts.mcpb).Hash -eq "b0c375e9eb7020ba1ec47e19b5684a9e87f339ae87870f4173a34f83d88ea5cc"
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 io.github.theluckystrike/receipts MCP server?
io.github.theluckystrike/receipts is an MCP server listed in the public MCP registry as io.github.theluckystrike/receipts. Parse raw receipt lines into itemized totals with tax. All data is local. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/receipts.mcpb).
Is the io.github.theluckystrike/receipts MCP server safe to use?
io.github.theluckystrike/receipts scores 53 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 io.github.theluckystrike/receipts MCP server expose?
io.github.theluckystrike/receipts exposes 1 tool: receipt_parse. Their descriptions and schemas cost roughly 53 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/receipts MCP server under?
io.github.theluckystrike/receipts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.