Remote MCP · Endpoint
uk.co.leaserenewalcost/site MCP server
Yes, as of 1 hour ago: the check failed for an unclassified reason.
DownLast checked 1 hour ago
Server URL
https://leaserenewalcost.co.uk/mcp
The last check failed: the check failed for an unclassified reason.
- Registry name
- uk.co.leaserenewalcost/site
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 23.5% from 17 checks
- Described by its publisher as
- Lease Renewal Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the check failed for an unclassified reason | — |
| 2 days ago | Failed - the check failed for an unclassified reason | — |
| 4 days ago | Handshake completed | 661 ms |
| 5 days ago | Failed - the check failed for an unclassified reason | — |
| 7 days ago | Failed - the check failed for an unclassified reason | — |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Failed - the check failed for an unclassified reason | — |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 13 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 17 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Handshake completed | 563 ms |
| 19 days ago | Handshake completed | 514 ms |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Handshake completed | 698 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 4 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 uk.co.leaserenewalcost/site and makes no claim about it beyond what these checks measured.