Remote MCP · Endpoint
com.hydrantly/site MCP server
No. com.hydrantly/site answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hydrantly.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.hydrantly/site
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 582 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Hydrantly: the site's own MCP server — dataset; every answer cites the site.
- Website
- https://hydrantly.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 582 ms |
| 18 hours ago | Handshake completed | 522 ms |
| 2 days ago | Handshake completed | 655 ms |
| 3 days ago | Handshake completed | 504 ms |
| 4 days ago | Handshake completed | 910 ms |
| 5 days ago | Handshake completed | 786 ms |
| 6 days ago | Handshake completed | 875 ms |
| 7 days ago | Handshake completed | 989 ms |
| 10 days ago | Handshake completed | 781 ms |
| 13 days ago | Handshake completed | 909 ms |
| 15 days ago | Handshake completed | 763 ms |
| 17 days ago | Handshake completed | 723 ms |
| 19 days ago | Handshake completed | 734 ms |
| 21 days ago | Handshake completed | 804 ms |
| 23 days ago | Handshake completed | 741 ms |
| 25 days ago | Handshake completed | 741 ms |
| 27 days ago | Handshake completed | 736 ms |
| 28 days ago | Handshake completed | 686 ms |
| 29 days ago | Handshake completed | 1.20 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.hydrantly/site and makes no claim about it beyond what these checks measured.