@lintsure/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
Its tool definitions changed since version 0.3.8. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @lintsure/mcp@0.3.10
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
scan path, frameworks, files, rules, status, limit, all, format
Scan 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_rule ruleId
Explain 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.classify euUsers, personalData, specialCategoryData, usesAI, generativeAI, interactsWithPeople, decisionArea, b2bCustomers, wantsCertification, digitalProductEU, mobileApp, healthDataUS, governmentCustomers, euConsumers, cardPayments, usMarket
Suggest 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.
explain_framework framework
Explain 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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=22 |
| Source | github.com/lintsure/lintsure |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-do6pIkYbWVQ6gh53nCkuRni0tL1sN+kQnV+QyQ9WER8TjbaU+ed99CrguAJi6+MHKS+H4tR98Jwc5lDiew103g== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.3.10 | 2026-11-16 | Starts with no setup | 4 |
| 0.3.8 | 2026-11-12 | Starts with no setup | 4 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40lintsure/mcp)
New version out? Ask for a fresh report.