Remote MCP · Endpoint

McpStamp Deposits MCP server

No. McpStamp Deposits answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/deposits

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/deposits
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
577 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Track client security and retainer deposits: hold, apply to an invoice, refund, statements.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Deposits
CheckedResultHandshake
1 hour agoHandshake completed577 ms
8 days agoHandshake completed496 ms
9 days agoHandshake completed588 ms
11 days agoHandshake completed33 ms
12 days agoHandshake completed122 ms
13 days agoHandshake completed754 ms
14 days agoHandshake completed45 ms
14 days agoHandshake completed106 ms
16 days agoHandshake completed1.59 s
19 days agoHandshake completed995 ms
21 days agoHandshake completed667 ms
24 days agoHandshake completed982 ms
26 days agoHandshake completed56 ms
28 days agoHandshake completed1.11 s

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