Remote MCP · Endpoint
io.github.seanthings/hermes-real-estate-data MCP server
No. io.github.seanthings/hermes-real-estate-data answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hermes-storefront.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.seanthings/hermes-real-estate-data
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 131 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Typed US real-estate feeds: deals, signals, leads. Empty is explained, never pay for a blank.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 131 ms |
| 10 hours ago | Handshake completed | 182 ms |
| 1 day ago | Handshake completed | 140 ms |
| 2 days ago | Handshake completed | 129 ms |
| 4 days ago | Handshake completed | 250 ms |
| 4 days ago | Handshake completed | 134 ms |
| 5 days ago | Handshake completed | 126 ms |
| 6 days ago | Handshake completed | 247 ms |
| 8 days ago | Handshake completed | 178 ms |
| 11 days ago | Handshake completed | 297 ms |
| 13 days ago | Handshake completed | 282 ms |
| 16 days ago | Handshake completed | 207 ms |
| 18 days ago | Handshake completed | 133 ms |
| 20 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 280 ms |
| 24 days ago | Handshake completed | 261 ms |
| 26 days ago | Handshake completed | 250 ms |
| 27 days ago | Handshake completed | 144 ms |
| 29 days ago | Handshake completed | 144 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 io.github.seanthings/hermes-real-estate-data and makes no claim about it beyond what these checks measured.