Remote MCP · Endpoint

FAI Legal Research MCP server

No. FAI Legal Research answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://failegal.site/mcp

The last check completed an MCP handshake.

Registry name
site.failegal/fai-legal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
328 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Pakistani case law and statutes: Supreme Court and High Court judgments, laws, drafting templates.
Listing
From the official MCP registry (active).
Recent checks of FAI Legal Research
CheckedResultHandshake
1 hour agoHandshake completed328 ms
1 day agoHandshake completed910 ms
4 days agoHandshake completed871 ms
6 days agoHandshake completed908 ms
9 days agoHandshake completed818 ms
11 days agoHandshake completed424 ms
13 days agoHandshake completed897 ms
15 days agoHandshake completed1.67 s
17 days agoHandshake completed34 ms
19 days agoHandshake completed889 ms
21 days agoHandshake completed39 ms
22 days agoHandshake completed23 ms
24 days agoHandshake completed24 ms
25 days agoHandshake completed24 ms
27 days agoHandshake completed315 ms

The last 15 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 FAI Legal Research and makes no claim about it beyond what these checks measured.