Remote MCP · Endpoint
法老在线 LawBotter MCP server
No. 法老在线 LawBotter answered an MCP handshake 17 hours ago.
UpLast checked 17 hours ago
Server URL
https://lawbotter.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.lawbotter/lawbotter
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 785 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 1 check from 1 check
- Described by its publisher as
- 中文法律 MCP 服务：47,606 条法规与 11,369 条案例，提供法规检索、法条详情、法律问答、法律咨询与多轮追问。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 17 hours ago | Handshake completed | 785 ms |
The last 1 check. Full history is kept for 30 days; the all-time counter stands at 1 responding of 1.
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 法老在线 LawBotter and makes no claim about it beyond what these checks measured.