Remote MCP · Endpoint

McpStamp Petty Cash MCP server

No. McpStamp Petty Cash answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://mcp.zovo.one/mcp/petty-cash

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/petty-cash
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
592 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Run a petty cash float: numbered vouchers, cash counts, over and short, replenishment amounts.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Petty Cash
CheckedResultHandshake
22 minutes agoHandshake completed592 ms
9 days agoHandshake completed826 ms
9 days agoHandshake completed1.11 s
11 days agoHandshake completed60 ms
12 days agoHandshake completed1.49 s
13 days agoHandshake completed1.06 s
14 days agoHandshake completed832 ms
15 days agoHandshake completed49 ms
16 days agoHandshake completed92 ms
19 days agoHandshake completed35 ms
22 days agoHandshake completed76 ms
24 days agoHandshake completed56 ms
26 days agoHandshake completed29 ms
28 days agoHandshake completed222 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 Petty Cash and makes no claim about it beyond what these checks measured.