io.github.theluckystrike/expense-tracker
MCPB · EXPENSE-TRACKER.MCPB
Log expenses, receipts and mileage from chat: auto-categorise, split VAT, summarise, export, rebill.
Available components
Last scanned (18 hours ago)
Scores higher than 95% 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 92 of 93 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 92 of 93 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2389 tokens (~159/item across 15 items; 14 tools + 1 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% 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 15 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
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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 SecurityNo 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.
- Provenance in Provenance & TransparencyBuild provenance not yet verified.
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 →
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.
- 5 Nov 26 0
- Provenance: fail → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 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.
- 16 Oct 26 +55
- Provenance: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. 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
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.93 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Licence: MIT functional
- Package version: 0.22.5 → 0.22.9 functional
- Package version: 0.22.0 → 0.22.9 functional
- Package version: 0.22.0 → 0.22.5 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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.9/expense-tracker.mcpb@0.22.9
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 | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
category_rules Category rules ~82
Replace the merchant-to-category rules, or call with no rules to list them. Returns the stored rule list. The rules are applied by expense_add whenever a call gives no category of its own.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | – | The FULL rule list; it replaces the stored one, so include the rules you want to keep. Omit to list the current rules instead |
No output schema declared.
No examples provided.
expense_add Add an expense ~338
Record one expense and return its id, its net/VAT split and its billable flag. The response states every default that was applied, so the caller can see what was assumed rather than having to guess.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Gross amount on the receipt, in major units, e.g. 12.34. It is stored as integer minor units in the expense's own currency, so nothing is lost to floating point. |
| billable | boolean | – | Rebillable to the client. Default: true when project is given (a receipt booked to a client project is normally rebilled), false otherwise. Pass it explicitly to override. |
| category | string | – | Category, e.g. software, travel, office. Omit and the stored category rules are matched against the merchant to fill it in |
| currency | string | – | ISO code. Defaults to your expense_settings default_currency, else the shared business profile's default_currency, else EUR |
| date | string | – | ISO date YYYY-MM-DD, default today |
| merchant | string | – | Who was paid, e.g. Adobe |
| note | string | – | – |
| project | string | – | Project or client this belongs to |
| receipt_path | string | – | Absolute path to the receipt file; it is checked and hashed |
| tax_rate | number | – | Alias for vat_rate |
| vat | number | – | Alias for vat_rate |
| vat_rate | number | – | VAT percent already included in amount; it splits the gross into net and VAT. Omit to use the expense_settings default, or get no split at all when none is set |
No output schema declared.
No examples provided.
expense_delete Delete an expense ~55
Delete one expense by id and report what went. The receipt FILE stays on disk. Deleting a rebilled expense loses the record of what an invoice charged, so correct it with expense_update instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
expense_export Export expenses ~136
Call this tool to write manually logged receipts to a csv, xlsx or json file. Returns the path. Bank transactions for the period are exported by bank-statement's statement_export tool, not this one.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | – |
| category | string | – | – |
| format | string | yes | – |
| from | string | yes | ISO date, inclusive |
| path | string | – | Absolute path to write to; a leading ~ is expanded and missing parent directories are created. Default is an exports folder in the server data directory |
| project | string | – | – |
| to | string | yes | ISO date, inclusive |
No output schema declared.
No examples provided.
expense_list List expenses ~98
List expenses in a date range with each one's net/VAT split, category, merchant, project and billable flag, plus a total per currency. Free reads the last 30 days and says when your range predates it.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | – |
| category | string | – | – |
| from | string | – | ISO date, inclusive |
| project | string | – | – |
| to | string | – | ISO date, inclusive |
No output schema declared.
No examples provided.
expense_mark_rebilled Mark expenses as rebilled ~200
Mark expenses as rebilled once the invoice that carries them actually exists. Pass the expense_ids of one currency group from expense_to_invoice, or that project, date range and currency. Returns what was marked.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Required when marking by range: one invoice carries one currency. A range marks only billable, not-yet-rebilled expenses in this one currency, so invoicing the EUR group cannot mark the PLN one |
| from | string | – | ISO date, inclusive |
| ids | array | – | Expense ids, as returned per currency by expense_to_invoice. Takes precedence over project/from/to |
| invoice_number | string | yes | Invoice the expenses were billed on. Required: the marker records WHICH invoice carries each expense, and it is stored on every expense marked |
| project | string | – | Project rebilled, used with from, to and currency |
| to | string | – | ISO date, inclusive |
No output schema declared.
No examples provided.
expense_settings Expense defaults ~145
Read or set the defaults expense_add uses when a call does not name them: default_vat_rate and default_currency. Returns the stored defaults. Call with no arguments to read them without changing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| default_currency | string | – | ISO 4217 code to assume when a call gives none, e.g. EUR. Default EUR |
| default_vat_rate | number | – | VAT percent already included in a receipt, e.g. 23 in Poland, 19 in Germany. Set it once and every later expense gets its net/VAT split without the caller repeating the rate. It applies when the expe… |
No output schema declared.
No examples provided.
expense_summary Summarise expenses ~103
Totals for a date range grouped by category, project, month or merchant, per currency with gross, net and VAT, never mixed. Receipts only; bank transactions are totalled by bank-statement's statement_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | – |
| from | string | yes | ISO date, inclusive |
| group_by | string | yes | How to group the totals |
| project | string | – | – |
| to | string | yes | ISO date, inclusive |
No output schema declared.
No examples provided.
expense_to_invoice Rebill expenses to an invoice ~433
Preview the unbilled billable expenses of one project as invoice_create line items (description, quantity, unit_price, tax_rate), grouped per currency. Read-only: nothing is marked rebilled here.
| Name | Type | Req | Description |
|---|---|---|---|
| assume_vat_rate | number | – | Split expenses that recorded NO VAT rate at this percent, flagged in the description. Only applied when you pass it here. An expense with no rate holds a GROSS amount and is otherwise rebilled as-is… |
| from | string | yes | ISO date, inclusive |
| fx_rates | object | – | Rate per source currency, meaning 1 unit of that currency = X units of target_currency, e.g. {"EUR": 1.08, "GBP": 1.27}. You supply the rate; nothing here fetches or guesses one. Omit it when the ran… |
| include_rebilled | boolean | – | Include expenses already marked as rebilled, default false |
| markup_percent | number | – | Percent added to each net amount. Every line's unit_price is the NET amount and its tax_rate is the VAT rate recorded on the expense, so the invoice recomputes the same tax instead of charging it twi… |
| project | string | yes | Project or client to rebill |
| target_currency | string | – | Convert every line into this currency and return ONE group, e.g. "USD". Needs fx_rates for each other currency present. Lines are otherwise grouped per currency, because one invoice carries one curre… |
| to | string | yes | ISO date, inclusive |
No output schema declared.
No examples provided.
expense_update Update an expense ~194
Change one expense by id; only the fields you pass move. amount is in MAJOR units. A rebilled expense refuses an amount, currency or vat_rate edit unless unlink_rebill drops the invoice link.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| billable | boolean | – | – |
| category | string | – | – |
| currency | string | – | – |
| date | string | – | – |
| id | string | yes | Expense id from expense_add or expense_list |
| merchant | string | – | – |
| note | string | – | – |
| project | string | – | – |
| rebilled | boolean | – | false clears the rebilled marker and the invoice number, so the expense can be billed again |
| unlink_rebill | boolean | – | Allow editing amount, currency or vat_rate on a rebilled expense. Clears rebilled_at and rebilled_invoice, because the invoice no longer matches |
| vat_rate | number | – | – |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mileage_add Add a mileage claim ~359
Record a business trip as an expense, priced as distance x rate. Give exactly one of km or miles. Returns the saved id with the rate used, where that rate came from and the money, in the rate's own currency.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Whether the trip is rebilled to the client. Default true, so a mileage claim reaches expense_to_invoice unless you pass false |
| currency | string | – | Currency for your own rate. Only accepted together with rate_per_km; a table rate keeps the table currency |
| date | string | – | ISO date, default today |
| km | number | – | Distance in kilometres. Give exactly one of km or miles |
| miles | number | – | Distance in miles. Give exactly one of km or miles |
| project | string | – | Bill the trip to a client or project - use the same name you use in time-tracker and expense_add. Without it the drive is invisible to expense_summary by project and to expense_to_invoice |
| purpose | string | yes | Why the trip was made, e.g. client meeting in Krakow |
| rate_per_km | number | – | Your own rate per supplied unit, overriding the table. Pass it whenever you need your exact scheme rather than the approximate table rate |
| region | string | – | Which built-in table rate to use: PL 1.15 PLN/km, UK 0.45 GBP/mile, US 0.70 USD/mile, EU 0.30 EUR/km. Default US for miles, EU for km. Each is one flat approximate rate per region with no effective d… |
No output schema declared.
No examples provided.
receipt_attach Attach a receipt ~99
Call this tool to attach a receipt file to a stored expense. Returns the stored path and sha256. The file must exist; it is hashed so a later audit can prove the file has not changed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Expense id from expense_add or expense_list |
| path | string | yes | Path to the receipt file. It must already exist; a leading ~ is expanded. The path and its sha256 are stored on the expense |
No output schema declared.
No examples provided.
How do I install the io.github.theluckystrike/expense-tracker MCP server?
io.github.theluckystrike/expense-tracker 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, 363ef8958bf7fbc4022488ae5af885a6087ddac45b71e431234e348359e48048; the commands to do that are on this page. If it does not match, do not open it.
mcpb · expense-tracker.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
363ef8958bf7fbc4022488ae5af885a6087ddac45b71e431234e348359e48048
macOS / Linux
echo "363ef8958bf7fbc4022488ae5af885a6087ddac45b71e431234e348359e48048 expense-tracker.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\expense-tracker.mcpb).Hash -eq "363ef8958bf7fbc4022488ae5af885a6087ddac45b71e431234e348359e48048"
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/expense-tracker MCP server?
io.github.theluckystrike/expense-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/expense-tracker. Log expenses, receipts and mileage from chat: auto-categorise, split VAT, summarise, export, rebill. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.9/expense-tracker.mcpb).
Is the io.github.theluckystrike/expense-tracker MCP server safe to use?
io.github.theluckystrike/expense-tracker scores 61 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/expense-tracker MCP server expose?
io.github.theluckystrike/expense-tracker exposes 14 tools: expense_add, expense_list, expense_update, expense_delete, receipt_attach, and 9 more. Their descriptions and schemas cost roughly 2,367 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/expense-tracker MCP server under?
io.github.theluckystrike/expense-tracker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.theluckystrike/expense-tracker MCP server?
VerifyMCP ran 14 checks on io.github.theluckystrike/expense-tracker, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.theluckystrike/expense-tracker: Malware scan and Provenance. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.