Lintsure

io.github.lintsurePublished by GitHub account lintsurev0.2.0Updated Nov 8, 2026

Compliance readiness checks for code: EU AI Act, GDPR, SOC 2, ISO 27001. Local. Not legal advice.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lintsure is a local MCP server that lets a coding agent check a repository for compliance readiness against frameworks such as the EU AI Act, GDPR, SOC 2 and…

What you can do
  • Scan a repository for compliance readiness issues
  • Classify findings against the relevant frameworks
  • Explain what a framework covers and what a specific rule means
  • Runs locally over stdio and reports results to the agent in the conversation
When to use it
Useful when you want a coding agent to flag compliance-related gaps in a codebase before review, or to explain which rules and frameworks apply. It is a readiness aid, not an audit, certification or legal advice, so a person still makes the final call.
Requirements
Runs as a local process over stdio, installed from the npm package @lintsure/mcp (for example via npx), so Node.js and network access for the package download are needed. No authentication, environment variables or headers are declared.
Before you install
The README states it never writes files and never uploads your code, but it still reads repository contents locally. Its output is explicitly not an audit, certification or legal advice, and the server instructs the agent not to declare you compliant or certified and to ask before changing anything; treat findings as a starting point for human review.

Installation

In SourceWeft

  1. Open Lintsure in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@lintsure/mcp

Lintsure as an MCP server for Claude Code, Cursor, Codex, Windsurf and other MCP clients. Runs on your machine over stdio, never writes files, never uploads your code.

Lintsure is a readiness tool, not an audit, a certification or legal advice. It tells your coding agent not to call you compliant, certified or ready, not to decide for you, and to ask before changing anything. A person makes the final call.

bash
claude mcp add lintsure -- npx -y @lintsure/mcp

Then ask your agent: check this repo for compliance.

Tools: scan, classify, explain_framework, explain_rule. Setup for Cursor, Codex and Windsurf: https://lintsure.com/docs/mcp

Source: https://github.com/lintsure/lintsure · Apache-2.0

Source: packages/mcp/README.md at commit 684b8ab

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestNov 8, 2026

Score

50% 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 days25 pts

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

  • Auth declared10 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
  • License10 pts