Remote MCP · Endpoint

Realty.Bingo MCP server

No. Realty.Bingo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://realty.bingo/mcp

The last check completed an MCP handshake.

Registry name
io.github.agentstructure/realty
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Property search, comparison, investment analysis and watchlists with change alerts
Listing
From the official MCP registry (active).
Recent checks of Realty.Bingo
CheckedResultHandshake
1 hour agoHandshake completed93 ms
16 hours agoHandshake completed72 ms
2 days agoHandshake completed774 ms
3 days agoHandshake completed152 ms
4 days agoHandshake completed111 ms
5 days agoHandshake completed197 ms
6 days agoHandshake completed104 ms
8 days agoHandshake completed93 ms
10 days agoHandshake completed64 ms
13 days agoHandshake completed109 ms
15 days agoHandshake completed122 ms
17 days agoHandshake completed128 ms
19 days agoHandshake completed98 ms
21 days agoHandshake completed55 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 Realty.Bingo and makes no claim about it beyond what these checks measured.