Loading the registry…
MCP Server for Doclasana documentation platform integration with AI-powered IDEs
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: doclasana-mcp-server @ 1.0.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- doclasana-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
3 findings · 7.9s
v0.3.74
7 findings · 1.2s
v0.1.0
2 findings · 3.4s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 8.0s
v0.71.0
33 findings · 0.3s
v2.3.8
47 findings · 7.5s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged44 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 92 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 29 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
2 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/index.ts · reported by nerlo-behavioral
1 AAK-MCP-CLINE-CVE-2026-59723-001
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-58754
Files: package-lock.json · reported by trivy
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2026-40175
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42036
Files: package-lock.json · reported by trivy
1 CVE-2026-42037
Files: package-lock.json · reported by trivy
1 CVE-2026-42038
Files: package-lock.json · reported by trivy
1 CVE-2026-42039
Files: package-lock.json · reported by trivy
1 CVE-2026-42040
Files: package-lock.json · reported by trivy
1 CVE-2026-42041
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-42043
Files: package-lock.json · reported by trivy
1 CVE-2026-42044
Files: package-lock.json · reported by trivy
1 CVE-2026-44486
Files: package-lock.json · reported by trivy
1 CVE-2026-44488
Files: package-lock.json · reported by trivy
1 CVE-2026-44490
Files: package-lock.json · reported by trivy
1 CVE-2026-44495
Files: package-lock.json · reported by trivy
1 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
26 The model's answer could not be read.
Rules: GHSA-fjxv-7rqg-78g4, CVE-2025-7783, AAK-ANTHROPIC-SDK-001 and 22 more · Files: /repo/package-lock.json, package-lock.json, src/index.ts and 2 more · reported by osv-scanner, trivy, agent-audit-kit
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical vulnerabilities present in artifact dependencies
The artifact contains critical and high severity vulnerabilities within its installed dependencies, primarily identified in `package-lock.json`. Additionally, the artifact's source code in `src/` indicates the use of an SDK that may involve network egress for API calls and potential handling of credentials. A DNS rebinding vulnerability is also noted in `package.json`, which could facilitate unauthorized network access.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 25; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.