# io.github.theluckystrike/travel-allowance (mcpb · per-diem.mcpb)

Work out the travel allowance for a trip on official Polish, UK and US rate tables.

- Trust score: 54/100 (low)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- mcpb · `per-diem.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m.md), [page](https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/per-diem.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1565 tokens (~156/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "trip_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/per-diem.mcpb`

## 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 54, +1)

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

### 2026-09-19 (score 53, +1)

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

### 2026-09-17 (score 52, +1)

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

### 2026-09-15 (score 51, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 47)

First indexed and scored.

## MCP tools (9)

### `perdiem_rates` (~128 tokens)

List the bundled per diem rates

List a scheme's bundled daily allowance rates with the authority, instrument, source URL and effective date they came from. Filter by country or city. Free and unlimited.

Input parameters:

- `city` (string): City or locality name, for the schemes that publish per-city rates
- `country` (string): Country name or ISO code, e.g. Germany or DE. Matched exactly first, then as a substring
- `scheme` (string): "pl" Polish delegation regulation, "uk" HMRC benchmark scale rates, "us" GSA CONUS standard. Omit for every scheme

### `perdiem_calc` (~397 tokens)

Calculate a travel allowance

Calculate the daily travel allowance for one trip: the amount per day and the total in the scheme's currency, with the partial-day fraction and the meal deductions the scheme's own rule applies. Free and unlimited.

Input parameters:

- `destination` (string, required): Country or locality, e.g. "Germany", "Poland", "United Kingdom", "United States"
- `end` (string, required): When it ended, same form as start. It must be after start as an instant
- `fiscal_year` (string): US only, e.g. "FY2025". Defaults to the current bundled fiscal year
- `late_evening` (array): UK only, per day: the journey was ongoing at 8pm and a meal was bought after it, which adds the 10.00 GBP supplement
- `lodging_nights` (integer): Nights of accommodation. What this pays depends on the scheme and the answer says so
- `meals_provided` (array): Per day, in order: the free meals the traveller was given that day, e.g. [["breakfast"],["breakfast","lunch"]]. Each one reduces that day's allowance by the scheme's own percentage or amount
- `meals_provided_daily`: The same free meals on every day. Ignored for any day that meals_provided already names
- `scheme` (string, required): "pl" Polish delegation regulation, "uk" HMRC benchmark scale rates, "us" GSA CONUS standard
- `start` (string, required): When the trip began, ISO 8601 WITH a zone: "2026-03-28T22:00:00+01:00", or "2026-03-28T22:00" together with timezone
- `timezone` (string): IANA id such as "Europe/Warsaw". Required when start or end carries no offset; also the zone the US scheme counts calendar days in

### `trip_record` (~473 tokens)

Save a calculated trip

Calculate a trip and save it under a name, with the traveller taken from the shared business profile. Returns the TRIP-YYYY-NNNN id. Free tier: 5 trips a calendar month.

Input parameters:

- `destination` (string, required): Country or locality, e.g. "Germany", "Poland", "United Kingdom", "United States"
- `end` (string, required): When it ended, same form as start. It must be after start as an instant
- `fiscal_year` (string): US only, e.g. "FY2025". Defaults to the current bundled fiscal year
- `late_evening` (array): UK only, per day: the journey was ongoing at 8pm and a meal was bought after it, which adds the 10.00 GBP supplement
- `lodging_nights` (integer): Nights of accommodation. What this pays depends on the scheme and the answer says so
- `meals_provided` (array): Per day, in order: the free meals the traveller was given that day, e.g. [["breakfast"],["breakfast","lunch"]]. Each one reduces that day's allowance by the scheme's own percentage or amount
- `meals_provided_daily`: The same free meals on every day. Ignored for any day that meals_provided already names
- `name` (string, required): What to call it, e.g. "Berlin client workshop"
- `project` (string): Project or client this belongs to; carried onto the expense payload
- `purpose` (string): Why the trip happened; kept on the record and carried onto the expense payload
- `scheme` (string, required): "pl" Polish delegation regulation, "uk" HMRC benchmark scale rates, "us" GSA CONUS standard
- `start` (string, required): When the trip began, ISO 8601 WITH a zone: "2026-03-28T22:00:00+01:00", or "2026-03-28T22:00" together with timezone
- `timezone` (string): IANA id such as "Europe/Warsaw". Required when start or end carries no offset; also the zone the US scheme counts calendar days in
- `traveller` (string): Who travelled. Defaults to the shared business profile's name

### `trip_list` (~124 tokens)

List saved trips

List saved trips with the scheme, destination, dates and total on each, and a total per currency. Filter by scheme, destination, traveller, project and start date range. Free and unlimited.

Input parameters:

- `destination` (string): Only trips to a destination containing this text
- `from` (string): YYYY-MM-DD, earliest start date
- `project` (string): Only trips on this project
- `scheme` (string): Default "all"
- `to` (string): YYYY-MM-DD, latest start date
- `traveller` (string): Only trips by this traveller

### `trip_delete` (~91 tokens)

Delete a saved trip

Delete one saved trip that has not been exported and has no expense booked against it, and free the free-tier slot it held that month. A trip with a dependent is refused, named. Free and unlimited.

Input parameters:

- `trip` (string, required): Trip id such as TRIP-2026-0001, or an exact or partial trip name. A partial name matching more than one trip is refused with the list

### `trip_export` (~175 tokens)

Export a trip as expenses

Return the exact expense_add arguments for a saved trip, one payload per currency, ready to pass to the expense-tracker server. It writes nothing itself: see the note in the answer. Pro.

Input parameters:

- `billable` (boolean): Rebillable to the client. Default: true when the trip has a project, false otherwise
- `category` (string): Expense category to put on the payload. Default "travel"
- `mark_exported` (boolean): Stamp exported_at on the trip so a later export can see it already went out. Default false
- `split_lodging` (boolean): Return lodging as its own expense rather than folded into the subsistence total. Default true
- `trip` (string, required): Trip id such as TRIP-2026-0001, or an exact or partial trip name

### `perdiem_report` (~90 tokens)

Totals per scheme and month

Total the saved trips per scheme and per calendar month, in each scheme's own currency, with the day count and the trips behind every figure. Pro.

Input parameters:

- `from` (string): YYYY-MM, earliest month by start date
- `scheme` (string): Default "all"
- `to` (string): YYYY-MM, latest month by start date
- `traveller` (string): Only this traveller

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m#diagnostics

## Score history

- 2026-09-21: 54
- 2026-09-20: 53
- 2026-09-19: 53
- 2026-09-18: 52
- 2026-09-17: 52
- 2026-09-16: 51
- 2026-09-15: 51
- 2026-09-14: 47
- 2026-09-13: 47
- 2026-09-12: 47
- 2026-09-11: 47
- 2026-09-10: 47
- 2026-09-09: 47
- 2026-09-08: 47
- 2026-09-07: 47

## Common questions

### What is the io.github.theluckystrike/travel-allowance MCP server?

io.github.theluckystrike/travel-allowance is an MCP server listed in the public MCP registry as io.github.theluckystrike/travel-allowance. Work out the travel allowance for a trip on official Polish, UK and US rate tables. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/per-diem.mcpb).

### Is the io.github.theluckystrike/travel-allowance MCP server safe to use?

io.github.theluckystrike/travel-allowance scores 54 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/travel-allowance MCP server expose?

io.github.theluckystrike/travel-allowance exposes 9 tools: perdiem_rates, perdiem_calc, trip_record, trip_list, trip_delete, and 4 more. Their descriptions and schemas cost roughly 1,543 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/travel-allowance MCP server under?

io.github.theluckystrike/travel-allowance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/per-diem
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-travel-allowance/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-per-diem-m