Remote MCP · Endpoint

Contract Lily MCP server

No. Contract Lily answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api.contractlily.com/mcp

The last check completed an MCP handshake.

Registry name
com.contractlily/contract-lily
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
176 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
UK tenancy and employment rule checks: deposits, notice, rent increases, holiday and minimum wage.
Listing
From the official MCP registry (active).
Recent checks of Contract Lily
CheckedResultHandshake
37 minutes agoHandshake completed176 ms
4 days agoHandshake completed413 ms
7 days agoHandshake completed168 ms
16 days agoHandshake completed189 ms
16 days agoHandshake completed186 ms
18 days agoHandshake completed162 ms
19 days agoHandshake completed171 ms
20 days agoHandshake completed237 ms
21 days agoHandshake completed164 ms
22 days agoHandshake completed155 ms
23 days agoHandshake completed175 ms
26 days agoHandshake completed227 ms

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

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