McpStamp Per Diem
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Travel allowances from bundled Polish, HMRC and GSA rate tables, with partial days and meals.
Available components
Last scanned (23 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1815 tokens (~165/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 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 11 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
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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +69
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Oct 26 −68
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 4 Nov 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 | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/per-diem"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/per-diem"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/per-diem |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/per-diem |
| Authorisation server | https://mcp.zovo.one |
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.
How do I install the McpStamp Per Diem MCP server?
McpStamp 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'
What is the McpStamp Per Diem MCP server?
McpStamp Per Diem is an MCP server listed in the public MCP registry as io.github.theluckystrike/per-diem. Travel allowances from bundled Polish, HMRC and GSA rate tables, with partial days and meals. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/per-diem).
Is the McpStamp Per Diem MCP server safe to use?
McpStamp Per Diem scores 94 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 McpStamp Per Diem MCP server expose?
McpStamp 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 McpStamp Per Diem MCP server require authentication?
Yes. McpStamp 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 McpStamp Per Diem MCP server still maintained?
McpStamp Per Diem is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.