Remote MCP · Endpoint
com.hibot/hibot MCP server
No. com.hibot/hibot answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hibot.com/mcp/public
The last check completed an MCP handshake.
- Registry name
- com.hibot/hibot
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 397 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- HiBot public knowledge: the ANSWER framework for AI visibility, audit plans, case studies, research
- Website
- https://hibot.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 397 ms |
| 2 days ago | Handshake completed | 111 ms |
| 4 days ago | Handshake completed | 117 ms |
| 5 days ago | Handshake completed | 96 ms |
| 7 days ago | Handshake completed | 138 ms |
| 7 days ago | Handshake completed | 611 ms |
| 9 days ago | Handshake completed | 334 ms |
| 12 days ago | Handshake completed | 92 ms |
| 13 days ago | Handshake completed | 199 ms |
| 15 days ago | Handshake completed | 167 ms |
| 16 days ago | Handshake completed | 150 ms |
| 17 days ago | Handshake completed | 99 ms |
| 18 days ago | Handshake completed | 84 ms |
| 19 days ago | Handshake completed | 88 ms |
| 20 days ago | Handshake completed | 91 ms |
| 21 days ago | Handshake completed | 222 ms |
| 22 days ago | Handshake completed | 560 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 com.hibot/hibot and makes no claim about it beyond what these checks measured.