Skip to content
LexLint logo

LexLint MCP server

Which servers in the official MCP registry are LexLint's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to LexLint

Whose server it is
  • Registry nameio.lexlint/lexlintverified in the MCP registry

The registry name sits under lexlint.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Staterequires sign-inchecked 2026-10-19

On 2026-10-19 the server answered and asked for a sign-in with a LexLint account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "check an app's declared behaviour against jurisdiction laws", the likely first call is set_profile.
  • upload_lint_run change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer297 ms
  • Space in an agent's context≈ 6,780 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results1 of 8 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check an app's declared behaviour against jurisdiction laws
  • not sure · fix cheap legal issues in code before release
  • not sure · track incident notification deadlines in each jurisdiction

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: upload_lint_run

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.lexlint.io/mcp as a custom connector in the settings.

The first time it connects, the client opens a LexLint sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.