All servers / Developer / Lintsure MCP server
Lintsure MCP server
Lintsure MCP server for Claude Code, Cursor, Codex and Windsurf. Readiness checks, not an audit or legal advice.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 0.3.11. Package: @lintsure/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.7 seconds including download)
- Tools offered: 5
- Last published: 2026-11-18
- Weekly downloads (npm): 800
- License: Apache-2.0 · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
scan8 of 8 parameters describedScan a repository's source code for compliance and security gaps against the chosen frameworks. Use when the user asks things like 'is this ready to ship?', 'are we GDPR ready?' or 'check this repo for security issues'. By default returns a short list: Gaps first, each with file, line, rule, risk level and a one-line fix, plus counts and what was not covered. To check a fix, call it again with files and rules set to the file and rule you changed. Set format to "full" for the whole Markdown report and JSON. Read-only: it never changes files. Call classify first if you don't know which frameworks apply. Results are for a person to review, never a pass, certification or decision.
explain_rule1 of 1 parameter describedExplain one Lintsure rule in plain words: what it looks for, which framework controls it relates to (for example GDPR Art. 32 or OWASP A05), why it matters and how to fix it. Use after scan, when the user asks about a finding ('what does pii.logged mean?', 'why is this a problem?'). Returns text; read-only.
classify16 of 16 parameters describedSuggest which compliance frameworks may apply to a product, with a short reason for each, from a few yes/no answers about it. Use when the user asks 'which rules apply to us?' or before a first scan. Call it with no answers to get the questions to ask the user; then call it again with what you know and leave the rest out. Returns a list of frameworks to confirm with the user before running scan. Suggestions only: the user decides, ideally with a compliance professional. Read-only.
plan_checks1 of 1 parameter describedBefore writing a feature, list the Lintsure checks it is most likely to run into, with what each looks for and how to avoid it. Use when the user describes something to build ('add a file upload', 'a login page with Supabase', 'a chat with Claude'). Word matching, not a code review: it reads only the description. Returns text; read-only.
explain_framework1 of 1 parameter describedExplain a compliance framework in plain words: what it is, who it applies to, key dates (marked as already applying or upcoming), what it asks for, which parts Lintsure can check in code and which need work outside code. Use when the user asks 'what is the EU AI Act?', 'does the Cyber Resilience Act apply to us?', 'when does it apply?' or 'what does SOC 2 need from our code?', often before a scan. Returns text; read-only.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.