Remote MCP · Endpoint

Zovo Per Diem Calculator MCP server

No. Zovo Per Diem Calculator answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/zovo-per-diem-calculator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
403 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Travel allowance worksheets
Listing
From the official MCP registry (active).
Recent checks of Zovo Per Diem Calculator
CheckedResultHandshake
44 minutes agoHandshake completed403 ms
3 days agoHandshake completed216 ms
13 days agoHandshake completed316 ms
13 days agoHandshake completed559 ms
15 days agoHandshake completed329 ms
15 days agoHandshake completed263 ms
17 days agoHandshake completed434 ms
18 days agoHandshake completed301 ms
18 days agoHandshake completed248 ms
20 days agoHandshake completed310 ms
22 days agoHandshake completed258 ms
25 days agoHandshake completed291 ms
27 days agoHandshake completed251 ms

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

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 Zovo Per Diem Calculator and makes no claim about it beyond what these checks measured.