Remote MCP · Endpoint

io.github.theluckystrike/lease-schedule MCP server

No. io.github.theluckystrike/lease-schedule answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/lease-schedule

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/lease-schedule
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
40 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Lease schedules with a residual: the payment, the interest split and the journal per month.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/lease-schedule
CheckedResultHandshake
1 hour agoHandshake completed40 ms
2 days agoHandshake completed43 ms
4 days agoHandshake completed22 ms
6 days agoHandshake completed45 ms
7 days agoHandshake completed35 ms
9 days agoHandshake completed22 ms
10 days agoHandshake completed121 ms
11 days agoHandshake completed41 ms
14 days agoHandshake completed30 ms
16 days agoHandshake completed26 ms
17 days agoHandshake completed48 ms
19 days agoHandshake completed25 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed34 ms
22 days agoHandshake completed26 ms
22 days agoHandshake completed24 ms
24 days agoHandshake completed25 ms

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

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 io.github.theluckystrike/lease-schedule and makes no claim about it beyond what these checks measured.