Remote MCP · Endpoint

RealtyCrawl MCP server

No. RealtyCrawl answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://realtycrawl.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.realtycrawl/realtycrawl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
392 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search source-linked real estate observations with capability discovery and bounded credits.
Listing
From the official MCP registry (active).
Recent checks of RealtyCrawl
CheckedResultHandshake
1 day agoHandshake completed392 ms
1 day agoHandshake completed161 ms
2 days agoHandshake completed152 ms
4 days agoHandshake completed251 ms
5 days agoHandshake completed148 ms
6 days agoHandshake completed210 ms
7 days agoHandshake completed224 ms
8 days agoHandshake completed205 ms
9 days agoHandshake completed212 ms
12 days agoHandshake completed858 ms
15 days agoHandshake completed192 ms
17 days agoHandshake completed1.28 s
19 days agoHandshake completed1.27 s
21 days agoHandshake completed177 ms
23 days agoHandshake completed195 ms

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