io.github.theluckystrike/per-diem
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Daily travel allowances from bundled public rate tables: Poland, HMRC and GSA CONUS.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 10 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-per-diem 'https://mcp.zovo.one/mcp/per-diem'
{
"mcpServers": {
"theluckystrike-per-diem": {
"url": "https://mcp.zovo.one/mcp/per-diem"
}
}
} {
"servers": {
"theluckystrike-per-diem": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/per-diem"
}
}
} [mcp_servers.theluckystrike-per-diem] url = "https://mcp.zovo.one/mcp/per-diem"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-per-diem": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/per-diem",
"enabled": true
}
}
} openclaw mcp add theluckystrike-per-diem --url 'https://mcp.zovo.one/mcp/per-diem' --transport streamable-http
mcp_servers:
theluckystrike-per-diem:
url: "https://mcp.zovo.one/mcp/per-diem" {
"McpServers": {
"theluckystrike-per-diem": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/per-diem"
}
}
} assistant mcp add theluckystrike-per-diem -t streamable-http -u 'https://mcp.zovo.one/mcp/per-diem'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 0
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +1
- 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 security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/per-diem
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/per-diem | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/per-diem | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/per-diem |
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 →
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
perdiem_calc Calculate a travel allowance ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Country or locality, e.g. "Germany", "Poland", "United Kingdom", "United States" |
| end | string | yes | 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 | yes | "pl" Polish delegation regulation, "uk" HMRC benchmark scale rates, "us" GSA CONUS standard |
| start | string | yes | 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 |
No output schema declared.
No examples provided.
perdiem_rates List the bundled per diem rates ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
perdiem_report Totals per scheme and month ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
trip_delete Delete a saved trip ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trip | string | yes | 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 |
No output schema declared.
No examples provided.
trip_export Export a trip as expenses ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trip id such as TRIP-2026-0001, or an exact or partial trip name |
No output schema declared.
No examples provided.
trip_list List saved trips ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
trip_record Save a calculated trip ~482
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Country or locality, e.g. "Germany", "Poland", "United Kingdom", "United States" |
| end | string | yes | 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 | yes | 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 | yes | "pl" Polish delegation regulation, "uk" HMRC benchmark scale rates, "us" GSA CONUS standard |
| start | string | yes | 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 |
No output schema declared.
No examples provided.
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 82 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.