Remote MCP · Endpoint
好啦体检 MCP MCP server
Yes, as of 1 hour ago: the request timed out.
DownLast checked 1 hour ago
Server URL
https://ai.ihaola.com.cn/api/mcp/haola-pe
The last check failed: the request timed out.
- Registry name
- cn.com.ihaola/health-checkup-planner
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 25 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 企业团检分档报价与企业咨询、个人体检方案推荐、门店查询、体检预约、订单与体检件查询、体检常见问题。合作体检机构 800+ 门店，覆盖 240+ 城市，其中 540+ 门店支持 AI 直接查询与预约。
- Website
- https://www.ihaola.com.cn/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the request timed out | — |
| 13 hours ago | Handshake completed | 801 ms |
| 1 day ago | Handshake completed | 1.64 s |
| 2 days ago | Handshake completed | 751 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 4.
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 好啦体检 MCP and makes no claim about it beyond what these checks measured.