Remote MCP · Endpoint

McpStamp Per Diem MCP server

No. McpStamp Per Diem answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.zovo.one/mcp/per-diem

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/per-diem
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
609 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Travel allowances from bundled Polish, HMRC and GSA rate tables, with partial days and meals.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Per Diem
CheckedResultHandshake
20 minutes agoHandshake completed609 ms
9 days agoHandshake completed86 ms
9 days agoHandshake completed611 ms
11 days agoHandshake completed503 ms
12 days agoHandshake completed639 ms
13 days agoHandshake completed798 ms
14 days agoHandshake completed603 ms
15 days agoHandshake completed52 ms
16 days agoHandshake completed42 ms
19 days agoHandshake completed119 ms
21 days agoHandshake completed40 ms
24 days agoHandshake completed50 ms
26 days agoHandshake completed30 ms
28 days agoHandshake completed169 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with McpStamp Per Diem and makes no claim about it beyond what these checks measured.