Remote MCP · Endpoint

RenterCheck MCP server

No. RenterCheck answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

https://rentercheck.co.uk/api/mcp

The last check completed an MCP handshake.

Registry name
uk.co.rentercheck/rentercheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
240 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check a home to rent in England: rent, licensing, flood risk, energy rating and the free report.
Listing
From the official MCP registry (active).
Recent checks of RenterCheck
CheckedResultHandshake
23 minutes agoHandshake completed240 ms
9 days agoHandshake completed256 ms
10 days agoHandshake completed438 ms
11 days agoHandshake completed245 ms
12 days agoHandshake completed237 ms
14 days agoHandshake completed311 ms
14 days agoHandshake completed248 ms
15 days agoHandshake completed219 ms
17 days agoHandshake completed226 ms
19 days agoHandshake completed222 ms
21 days agoHandshake completed314 ms
24 days agoHandshake completed337 ms
26 days agoHandshake completed234 ms
28 days agoHandshake completed267 ms

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

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