Remote MCP · Endpoint

法老在线 LawBotter MCP server

No. 法老在线 LawBotter answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
782 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
中文法律 MCP 服务：47,606 条法规与 11,369 条案例，提供法规检索、法条详情、法律问答、法律咨询与多轮追问。
Listing
From the official MCP registry (active).
Recent checks of 法老在线 LawBotter
CheckedResultHandshake
34 minutes agoHandshake completed782 ms
9 days agoHandshake completed774 ms
10 days agoHandshake completed806 ms
11 days agoHandshake completed1.18 s
12 days agoHandshake completed816 ms
14 days agoHandshake completed795 ms
14 days agoHandshake completed793 ms
15 days agoHandshake completed781 ms
17 days agoHandshake completed772 ms
19 days agoHandshake completed841 ms
21 days agoHandshake completed1.97 s
24 days agoHandshake completed819 ms
26 days agoHandshake completed785 ms

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

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 法老在线 LawBotter and makes no claim about it beyond what these checks measured.