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
332 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 19 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).
Recent checks of com.hibot/hibot
CheckedResultHandshake
1 hour agoHandshake completed332 ms
19 hours agoHandshake completed149 ms
2 days agoHandshake completed130 ms
3 days agoHandshake completed105 ms
4 days agoHandshake completed118 ms
5 days agoHandshake completed101 ms
6 days agoHandshake completed122 ms
8 days agoHandshake completed1.05 s
10 days agoHandshake completed114 ms
13 days agoHandshake completed671 ms
15 days agoHandshake completed178 ms
17 days agoHandshake completed156 ms
19 days agoHandshake completed128 ms
21 days agoHandshake completed397 ms
23 days agoHandshake completed111 ms
25 days agoHandshake completed117 ms
27 days agoHandshake completed96 ms
28 days agoHandshake completed138 ms
29 days agoHandshake completed611 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.