Remote MCP · Endpoint

RedFlagLease MCP server

No. RedFlagLease answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://redflaglease.com/api/leasecheck/mcp

The last check completed an MCP handshake.

Registry name
com.redflaglease/lease-checker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
587 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check US leases for red flags and look up verified state tenant law with statute citations.
Listing
From the official MCP registry (active).
Recent checks of RedFlagLease
CheckedResultHandshake
52 minutes agoHandshake completed587 ms
3 days agoHandshake completed331 ms
12 days agoHandshake completed334 ms
13 days agoHandshake completed314 ms
14 days agoHandshake completed515 ms
15 days agoHandshake completed325 ms
17 days agoHandshake completed358 ms
18 days agoHandshake completed349 ms
18 days agoHandshake completed315 ms
20 days agoHandshake completed424 ms
22 days agoHandshake completed360 ms
25 days agoHandshake completed345 ms
27 days agoHandshake completed429 ms
29 days agoHandshake completed394 ms

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

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