Remote MCP · Endpoint

LeaseBreak MCP server

No. LeaseBreak answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lease-break.magicteams.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.everyai-com/lease-break
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
179 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Estimate early lease termination costs, compare options and draft notice letters. Free.
Listing
From the official MCP registry (active).
Recent checks of LeaseBreak
CheckedResultHandshake
1 hour agoHandshake completed179 ms
2 days agoHandshake completed154 ms
5 days agoHandshake completed75 ms
7 days agoHandshake completed103 ms
9 days agoHandshake completed92 ms
11 days agoHandshake completed91 ms
13 days agoHandshake completed79 ms
15 days agoHandshake completed83 ms
17 days agoHandshake completed44 ms
19 days agoHandshake completed106 ms
20 days agoHandshake completed96 ms
21 days agoHandshake completed71 ms
23 days agoHandshake completed57 ms

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

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