Remote MCP · Endpoint

Realistimo MCP server

No. Realistimo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://realistimo.com/mcp

The last check completed an MCP handshake.

Registry name
com.realistimo/realistimo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
244 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free MCP server with Bulgarian property prices, rental yields, deal costs and neighbourhood profiles
Listing
From the official MCP registry (active).
Recent checks of Realistimo
CheckedResultHandshake
1 hour agoHandshake completed244 ms
8 days agoHandshake completed252 ms
9 days agoHandshake completed320 ms
11 days agoHandshake completed143 ms
12 days agoHandshake completed132 ms
12 days agoHandshake completed386 ms
14 days agoHandshake completed224 ms
14 days agoHandshake completed129 ms
16 days agoHandshake completed160 ms
19 days agoHandshake completed210 ms
21 days agoHandshake completed139 ms
24 days agoHandshake completed228 ms
26 days agoHandshake completed170 ms
28 days agoHandshake completed127 ms

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

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