Loading the registry…
A Model Context Protocol (MCP) server that enables secure interaction with Microsoft SQL Server databases.
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.
6 critical findings reported by cisco-skill-scanner, trivy, osv-scanner, 5 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
pypi: microsoft_sql_server_mcp @ 0.1.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- microsoft_sql_server_mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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.
v2.0.11
5 findings · 6.8s
v0.3.74
7 findings · 2.7s
v0.1.0
0 findings · 3.0s
v0.1.0
1 finding · 3.0s
v0.1.0
0 findings · 6.7s
v0.71.0
23 findings · 0.2s
v2.3.8
28 findings · 1.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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 ·n/a: not applicablecisco-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 64 findings across every scanner that examined this package. 1 of 6 findings rated critical by their scanner was among the dismissals.
Not reviewed is not the same as clean. Those 7 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, opt.nerlo-rules.nerlo-install-run-bundled-artifact, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/docs/deployment.md · reported by cisco-skill-scanner, nerlo-install-instruction
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/publish.yml, .github/workflows/ci.yml · reported by agent-audit-kit
2 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: YARA_sql_injection_generic, AAK-IPI-WILD-CORPUS-001 · Files: /repo/tests/unit/test_modules.py, tests/unit/test_modules.py · reported by cisco-skill-scanner, agent-audit-kit
The model could have called any of these a false positive and did not.
2 GHSA-c2jp-c369-7pvx
Files: requirements.txt, /repo/requirements.txt · reported by trivy, osv-scanner
2 GHSA-rcfx-77hg-w2wv
Files: requirements.txt, /repo/requirements.txt · reported by trivy, osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/server.py · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/config.py · reported by agent-audit-kit
1 CVE-2025-43859
Files: uv.lock · reported by trivy
1 CVE-2025-53365
7 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: PYSEC-2026-2120, PYSEC-2026-2121, GHSA-fj7x-q9j7-g6q6 and 4 more · Files: /repo/requirements-dev.txt, SECURITY.md, /repo/SKILL.md · reported by osv-scanner, agent-audit-kit, cisco-skill-scanner
Critical vulnerabilities and exposed secrets found.
The artifact contains critical vulnerabilities (e.g., PYSEC-2026-338, CVE-2025-43859) in its dependencies, which could lead to severe system compromise. Exposed secrets were identified in `src/config.py` (AAK-SECRET-004), potentially granting unauthorized credential access. The use of an Anthropic SDK in `src/server.py` (AAK-ANTHROPIC-SDK-001) suggests network egress for AI model interaction. Multiple other high-severity vulnerabilities are present across various dependency files.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 CVE-2025-53366
Files: uv.lock · reported by trivy
1 CVE-2025-54121
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-62800
Files: requirements.txt · reported by trivy
1 CVE-2025-62801
Files: requirements.txt · reported by trivy
1 CVE-2025-64340
Files: requirements.txt · reported by trivy
1 CVE-2025-66416
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: requirements.txt · reported by trivy
1 CVE-2026-27124
Files: requirements.txt · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: requirements.txt · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-52869
Files: uv.lock · reported by trivy
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 PYSEC-2026-1364
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1365
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1616
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1618
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2474
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
Showing 24 of 24; the rest are in the per-scanner reports above.