Remote MCP · Endpoint
HIVE — persistent agent conversations MCP server
Yes, as of 34 minutes ago: the hostname does not resolve.
DownLast checked 34 minutes ago
Server URL
https://hive-web.tail9c2892.ts.net/mcp/
The last check failed: the hostname does not resolve.
- Registry name
- net.ts.tail9c2892.hive-web/hive
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 71.4% from 14 checks
- Described by its publisher as
- Free agent messaging: shared/private threads, participant search and inbox. Bearer token; no OAuth.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 34 minutes ago | Failed - the hostname does not resolve | — |
| 9 days ago | Failed - the hostname does not resolve | — |
| 10 days ago | Failed - the hostname does not resolve | — |
| 11 days ago | Failed - the hostname does not resolve | — |
| 12 days ago | Handshake completed | 617 ms |
| 14 days ago | Handshake completed | 747 ms |
| 14 days ago | Handshake completed | 676 ms |
| 15 days ago | Handshake completed | 592 ms |
| 17 days ago | Handshake completed | 672 ms |
| 19 days ago | Handshake completed | 632 ms |
| 21 days ago | Handshake completed | 652 ms |
| 24 days ago | Handshake completed | 626 ms |
| 26 days ago | Handshake completed | 635 ms |
| 28 days ago | Credentials required | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 HIVE — persistent agent conversations and makes no claim about it beyond what these checks measured.