Remote MCP · Endpoint
HiveClear MCP server
No. HiveClear answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://hiveclear.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.srotzin/hiveclear
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 836 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Multi-agent settlement and clearing with validator consensus
- Website
- https://www.hiveagentiq.com/
- Repository
- https://github.com/srotzin/hiveclear
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 836 ms |
| 2 days ago | Handshake completed | 129 ms |
| 4 days ago | Handshake completed | 128 ms |
| 5 days ago | Handshake completed | 129 ms |
| 7 days ago | Handshake completed | 142 ms |
| 8 days ago | Handshake completed | 131 ms |
| 9 days ago | Handshake completed | 246 ms |
| 12 days ago | Handshake completed | 120 ms |
| 13 days ago | Handshake completed | 125 ms |
| 15 days ago | Handshake completed | 276 ms |
| 17 days ago | Handshake completed | 258 ms |
| 18 days ago | Handshake completed | 98 ms |
| 19 days ago | Handshake completed | 266 ms |
| 20 days ago | Handshake completed | 130 ms |
| 20 days ago | Handshake completed | 118 ms |
| 21 days ago | Handshake completed | 425 ms |
| 23 days ago | Handshake completed | 269 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 HiveClear and makes no claim about it beyond what these checks measured.