# io.github.theluckystrike/expense-tracker-receipts-mileage (remote · mcp.zovo.one)

Log expenses, receipts and mileage from chat: auto-categorise, split VAT, summarise, export, rebill.

- Trust score: 83/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker.md), [page](https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker)
- mcpb · `expense-tracker.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-expense-tr.md), [page](https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-expense-tr)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/expense-tracker`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2463 tokens (~153/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/expense-tracker-receipts-mileage MCP server?

io.github.theluckystrike/expense-tracker-receipts-mileage is a hosted endpoint at https://mcp.zovo.one/mcp/expense-tracker, 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-expense-tracker-receipts-mileage 'https://mcp.zovo.one/mcp/expense-tracker'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-expense-tracker-receipts-mileage": {
      "url": "https://mcp.zovo.one/mcp/expense-tracker"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-expense-tracker-receipts-mileage": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/expense-tracker"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-expense-tracker-receipts-mileage]
url = "https://mcp.zovo.one/mcp/expense-tracker"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-expense-tracker-receipts-mileage": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/expense-tracker",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-expense-tracker-receipts-mileage --url 'https://mcp.zovo.one/mcp/expense-tracker' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-expense-tracker-receipts-mileage:
    url: "https://mcp.zovo.one/mcp/expense-tracker"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-expense-tracker-receipts-mileage": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/expense-tracker"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-expense-tracker-receipts-mileage -t streamable-http -u 'https://mcp.zovo.one/mcp/expense-tracker'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-expense-tracker-receipts-mileage": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/expense-tracker"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 83, +2)

- [security] Tool “expense_delete” is now declared destructive
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-20 (score 81, +1)

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

### 2026-09-18 (score 80, +55)

- [security regression] Authorization: unverified → fail
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Stability: unverified → 0.30
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-17 (score 25, −54)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Transport: pass → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.23 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified

### 2026-09-16 (score 79, +1)

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

### 2026-09-14 (score 78, +1)

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

### 2026-09-12 (score 77, +1)

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

### 2026-09-11 (score 76, 0)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

## MCP tools (14)

### `expense_add` (~338 tokens)

Add an expense

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.

Input parameters:

- `amount` (number, required): 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

### `expense_list` (~98 tokens)

List expenses

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.

Input parameters:

- `billable` (boolean)
- `category` (string)
- `from` (string): ISO date, inclusive
- `project` (string)
- `to` (string): ISO date, inclusive

### `expense_update` (~194 tokens)

Update an expense

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.

Input parameters:

- `amount` (number)
- `billable` (boolean)
- `category` (string)
- `currency` (string)
- `date` (string)
- `id` (string, required): 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)

### `expense_delete` (~55 tokens)

Delete an expense

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.

Input parameters:

- `id` (string, required)

### `receipt_attach` (~128 tokens)

Attach a receipt

Not available on the hosted endpoint: it has no filesystem, so there is no receipt file to read or hash. Attach receipts on a local install instead - download expense-tracker.mcpb from https://github.com/theluckystrike/mcp-servers/releases/latest and open it in Claude Desktop - or record the receipt reference in the expense note.

Input parameters:

- `id` (string, required): Expense id from expense_add or expense_list
- `path` (string, required): Path to the receipt file. It must already exist; a leading ~ is expanded. The path and its sha256 are stored on the expense

### `category_rules` (~82 tokens)

Category rules

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.

Input parameters:

- `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

### `expense_settings` (~145 tokens)

Expense defaults

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.

Input parameters:

- `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…

### `expense_summary` (~103 tokens)

Summarise expenses

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.

Input parameters:

- `billable` (boolean)
- `from` (string, required): ISO date, inclusive
- `group_by` (string, required): How to group the totals
- `project` (string)
- `to` (string, required): ISO date, inclusive

### `mileage_add` (~359 tokens)

Add a mileage claim

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.

Input parameters:

- `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, required): 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…

### `expense_export` (~123 tokens)

Export expenses

Export the expenses in a date range as csv, xlsx or json and return a download link that is valid for one hour. Nothing partial is ever written: if a limit is hit no file is produced at all.

Input parameters:

- `billable` (boolean)
- `category` (string)
- `format` (string, required)
- `from` (string, required): ISO date, inclusive
- `path` (string): Optional file name for the download, e.g. q3.csv
- `project` (string)
- `to` (string, required): ISO date, inclusive

### `expense_to_invoice` (~433 tokens)

Rebill expenses to an invoice

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.

Input parameters:

- `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, required): 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, required): 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, required): ISO date, inclusive

### `expense_mark_rebilled` (~200 tokens)

Mark expenses as rebilled

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.

Input parameters:

- `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, required): 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

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 25
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36

## Common questions

### What is the io.github.theluckystrike/expense-tracker-receipts-mileage MCP server?

io.github.theluckystrike/expense-tracker-receipts-mileage is an MCP server listed in the public MCP registry as io.github.theluckystrike/expense-tracker-receipts-mileage. Log expenses, receipts and mileage from chat: auto-categorise, split VAT, summarise, export, rebill. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/expense-tracker).

### Is the io.github.theluckystrike/expense-tracker-receipts-mileage MCP server safe to use?

io.github.theluckystrike/expense-tracker-receipts-mileage scores 83 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 io.github.theluckystrike/expense-tracker-receipts-mileage MCP server expose?

io.github.theluckystrike/expense-tracker-receipts-mileage exposes 14 tools: expense_add, expense_list, expense_update, expense_delete, receipt_attach, and 9 more. Their descriptions and schemas cost roughly 2,389 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/expense-tracker-receipts-mileage MCP server require authentication?

Yes. io.github.theluckystrike/expense-tracker-receipts-mileage 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 io.github.theluckystrike/expense-tracker-receipts-mileage MCP server still maintained?

io.github.theluckystrike/expense-tracker-receipts-mileage is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/expense-tracker
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/expense-tracker
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/expense-tracker
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-expense-tracker-receipts-mileage/mcp-expense-tracker