Remote MCP · Endpoint

AI Law Framework MCP server

No. AI Law Framework answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://ailawframework.com/mcp

The last check completed an MCP handshake.

Registry name
com.ailawframework/ai-law-framework
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
520 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Decide whether AI may be used for a legal task, who drafts and who checks. Australian law.
Listing
From the official MCP registry (active).
Recent checks of AI Law Framework
CheckedResultHandshake
56 minutes agoHandshake completed520 ms
3 days agoHandshake completed474 ms
12 days agoHandshake completed501 ms
13 days agoHandshake completed434 ms
14 days agoHandshake completed546 ms
15 days agoHandshake completed550 ms
17 days agoHandshake completed767 ms
18 days agoHandshake completed821 ms
18 days agoHandshake completed940 ms
20 days agoHandshake completed1.78 s
22 days agoHandshake completed510 ms
25 days agoHandshake completed432 ms
27 days agoHandshake completed437 ms
29 days agoHandshake completed651 ms

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

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