Remote MCP · Endpoint

LexLint: compliance lint for AI, scraping, and privacy law MCP server

No. LexLint: compliance lint for AI, scraping, and privacy law answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.lexlint.org/mcp

The last check completed an MCP handshake.

Registry name
org.lexlint/lexlint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
630 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Compliance lint for AI, scraping, and privacy law. Cited findings in 200 or more jurisdictions.
Listing
From the official MCP registry (deprecated).
Recent checks of LexLint: compliance lint for AI, scraping, and privacy law
CheckedResultHandshake
1 hour agoHandshake completed630 ms
1 day agoHandshake completed366 ms
2 days agoHandshake completed350 ms
3 days agoHandshake completed250 ms
4 days agoHandshake completed722 ms
5 days agoHandshake completed320 ms
6 days agoHandshake completed793 ms
8 days agoHandshake completed778 ms
11 days agoHandshake completed934 ms
13 days agoHandshake completed615 ms
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
27 days agoCredentials required—
29 days agoCredentials required—
29 days agoCredentials required—

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

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 LexLint: compliance lint for AI, scraping, and privacy law and makes no claim about it beyond what these checks measured.