# io.github.theluckystrike/per-diem (remote · mcp.zovo.one)

Daily travel allowances from bundled public rate tables: Poland, HMRC and GSA CONUS.

- Trust score: 84/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`: 84/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-per-diem/mcp-per-diem.md), [page](https://verifymcp.io/servers/theluckystrike-per-diem/mcp-per-diem)
- mcpb · `per-diem.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-per-diem/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-per-diem-m.md), [page](https://verifymcp.io/servers/theluckystrike-per-diem/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-per-diem-m)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/per-diem`
- 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**: 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 1713 tokens (~155/item across 11 items; 9 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**: 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**: 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 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

### How do I install the io.github.theluckystrike/per-diem MCP server?

io.github.theluckystrike/per-diem is a hosted endpoint at https://mcp.zovo.one/mcp/per-diem, 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-per-diem 'https://mcp.zovo.one/mcp/per-diem'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-per-diem": {
      "url": "https://mcp.zovo.one/mcp/per-diem"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-per-diem": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/per-diem"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-per-diem]
url = "https://mcp.zovo.one/mcp/per-diem"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-per-diem --url 'https://mcp.zovo.one/mcp/per-diem' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-per-diem:
    url: "https://mcp.zovo.one/mcp/per-diem"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-per-diem": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/per-diem"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-per-diem -t streamable-http -u 'https://mcp.zovo.one/mcp/per-diem'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-per-diem": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/per-diem"
    }
  }
}
```

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 84, +2)

- [security] Tool “trip_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 82, +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 81, +1)

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

### 2026-09-17 (score 80, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 80, +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-13 (score 79, +1)

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

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

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

### 2026-09-10 (score 77, 0)

- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “perdiem_report” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “license_activate” reworded the description of “key”

## 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` (~482 tokens)

Save a calculated trip

Calculate a trip and save it under a name, traveller taken from the shared business profile; returns the TRIP-YYYY-NNNN id. An identical record is refused and named, spending no slot. Free: 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` (~93 tokens)

Delete a saved trip

Delete one saved trip and free the free-tier slot it held that month. A trip that has been exported or has an expense booked against it is refused with the blocker named, and nothing is written. 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` (~183 tokens)

Export a trip as expenses

Return the exact expense_add arguments for a saved trip: one payload for subsistence and, with split_lodging, one for lodging. It writes nothing in the expense-tracker server; only mark_exported changes this trip. 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` (~101 tokens)

Totals per scheme and month

Total saved trips per scheme and calendar month, bucketed by start date: trips, days, subsistence and lodging, each in the scheme's own currency, with the trip ids 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` (~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-per-diem/mcp-per-diem#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36

## Common questions

### What is the io.github.theluckystrike/per-diem MCP server?

io.github.theluckystrike/per-diem is an MCP server listed in the public MCP registry as io.github.theluckystrike/per-diem. Daily travel allowances from bundled public rate tables: Poland, HMRC and GSA CONUS. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/per-diem).

### Is the io.github.theluckystrike/per-diem MCP server safe to use?

io.github.theluckystrike/per-diem scores 84 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/per-diem MCP server expose?

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

### Does the io.github.theluckystrike/per-diem MCP server require authentication?

Yes. io.github.theluckystrike/per-diem 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/per-diem MCP server still maintained?

io.github.theluckystrike/per-diem 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/per-diem
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/per-diem
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/per-diem
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-per-diem/mcp-per-diem.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-per-diem/mcp-per-diem.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-per-diem/mcp-per-diem