Is the Lexlint MCP server down?

mcp-registry/org.lexlint/lexlint

Verdict. Lexlint MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 448 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (94/100) across 8 tools, costing an agent about 6,559 tokens to load. Checked every few minutes; no tool is ever called.

Data as of .

30-day measurements and how they compare with other MCP servers
MetricValueBetter than
Uptime, 30 days100%42% of MCP servers
Median handshake latency448 ms54% of MCP servers
p95 handshake latency1032 ms—
Checks in 30 days1,484—
Outages, 90 days0—
Median recovery——
Agent-readiness score94/100 (A)78% of MCP servers
Tools8—
Tool-list size for an agent~6,559 tokens35% of MCP servers
Days observed28—
healthy
Last checked 2026-10-26 20:38 UTC · handshake 506ms

As of 2026-10-26 20:38 UTC, the Lexlint MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
1,550
outages (90d)
0
tools
8

Compliance lint for AI, scraping, and privacy law. Cited findings in 200 or more jurisdictions.

Install Lexlint MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lexlint-mcp-server https://mcp.lexlint.io/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lexlint-mcp-server": {
      "type": "http",
      "url": "https://mcp.lexlint.io/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (94/100)

A (94/100): 0 error(s), 1 warning(s) across 8 tool(s); ~6,559 tokens of tool definitions.
Scores higher than 79% of 15,760 MCP servers Glimind has audited.
Its tool list costs an agent ~6,559 tokens per session — more than 65% of servers.
94 → 94 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost71
Client compatibility100
Protocol100
Reliability100
Stability72

What to fix (2)

3 tool definition(s) exceed ~1,200 tokens each (largest: run_lint, ~2,011).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,418 tokens every session. How to fix →

Tools: run_lint, set_profile, upload_lint_run · saves ~3,418 tokens/session

In the last 30 days: 0 tool(s) removed and 7 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.lexlint/lexlint"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.lexlint/lexlint"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.lexlint%2Flexlint.svg)](https://glimind.com/server/mcp-registry%2Forg.lexlint%2Flexlint?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Forg.lexlint%2Flexlint?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.lexlint%2Flexlint.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.lexlint%2Flexlint.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.lexlint%2Flexlint?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:616af038ab168ca4…, first seen 2026-10-26, included at leaf 70583 of 75,348. Version history · verify what your client received.

Tools (8)

Compare: most reliable other servers · most reliable security servers · most reliable knowledge servers · most reliable code servers · most reliable communication servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lexlint MCP server down right now?

As of 2026-10-26 20:38 UTC, the Lexlint MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lexlint MCP server provide?

Lexlint MCP server advertises 8 tools, including check_access, claim_trial_key, get_law, resolve_domain_jurisdiction, run_lint.

How do I install Lexlint MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.lexlint.io/mcp

Is the Lexlint MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lexlint MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve