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.io/mcp
The last check completed an MCP handshake.
- Registry name
- org.lexlint/lexlint
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 217 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.
- Website
- https://mcp.lexlint.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 217 ms |
| 1 day ago | Handshake completed | 544 ms |
| 2 days ago | Handshake completed | 199 ms |
| 3 days ago | Handshake completed | 165 ms |
| 4 days ago | Handshake completed | 362 ms |
| 5 days ago | Handshake completed | 164 ms |
| 6 days ago | Handshake completed | 620 ms |
| 8 days ago | Handshake completed | 348 ms |
| 11 days ago | Handshake completed | 304 ms |
| 13 days ago | Handshake completed | 183 ms |
| 15 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 24 days ago | Credentials required | — |
| 26 days ago | Credentials required | — |
| 27 days ago | Credentials required | — |
| 29 days ago | Credentials required | — |
| 29 days ago | Credentials required | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.
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.