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

org.lexlintPublished by lexlint.orgOfficial publisherv1.0.2Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that runs compliance lint checks on AI, scraping and privacy-law questions, returning cited findings across 200+ jurisdictions.

What you can do
  • Run compliance lint checks on AI, scraping and privacy-law questions.
  • Get findings that cite legal sources across 200 or more jurisdictions.
  • Check requests against an UnGovr Open Data key, which is metered per request.
When to use it
Useful when an assistant needs to flag legal or regulatory concerns in AI use, web scraping or privacy handling, and wants cited, jurisdiction-specific findings rather than general advice.
Requirements
Remote streamable HTTP endpoint at mcp.lexlint.io; no local runtime or package. Requires an X-API-Key header holding your own UnGovr Open Data key, which is checked against UnGovr's key store and metered per request.
Before you install
You must supply your own UnGovr Open Data key in the X-API-Key header; it is verified against UnGovr's key store and each request is metered against the key's allowance (account keys share a daily allowance with data.ungovr.org, trial keys are one-off). Queries are sent to a third-party service. Findings are informational and not a substitute for legal advice.

Installation

In SourceWeft

  1. Open LexLint: compliance lint for AI, scraping, and privacy law in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.lexlint%2Flexlint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lexlint-compliance-lint-for-ai-scraping": {
      "type": "http",
      "url": "https://mcp.lexlint.io/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

3
  1. v1.0.2LatestSep 29, 2026
  2. v1.0.1Sep 24, 2026
  3. v1.0.0Sep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.