Remote MCP · Endpoint

bitHuman docs MCP server

No. bitHuman docs answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://docs.bithuman.ai/docs-mcp

The last check completed an MCP handshake.

Registry name
ai.bithuman/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The bitHuman docs over MCP: two read-only tools, search and fetch; it needs no account and no key.
Listing
From the official MCP registry (active).
Recent checks of bitHuman docs
CheckedResultHandshake
53 minutes agoHandshake completed68 ms
3 days agoHandshake completed741 ms
12 days agoHandshake completed85 ms
13 days agoHandshake completed133 ms
15 days agoHandshake completed66 ms
15 days agoHandshake completed106 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed80 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed67 ms
22 days agoHandshake completed648 ms
25 days agoHandshake completed79 ms
27 days agoHandshake completed74 ms
29 days agoHandshake completed316 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 25.

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 bitHuman docs and makes no claim about it beyond what these checks measured.