Windows Screenshot MCP Server - Capture all screens or primary screen with Print Screen simulation
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- screenshot-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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 · 1.0s
v2.0.11
128 findings · 9.8s
v0.3.74
6 findings · 1.2s
v0.1.0
0 findings · 4.6s
v0.1.0
0 findings · 4.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.4s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 19, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 134 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 4 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.
62 YARA_embedded_pe_executable
Files: /repo/dist/Microsoft.Extensions.AI.Abstractions.dll, /repo/dist/Microsoft.Extensions.Configuration.Abstractions.dll, /repo/dist/Microsoft.Extensions.Configuration.Binder.dll and 28 more · reported by cisco-skill-scanner
31 BINARY_FILE_DETECTED
Files: /repo/dist/Microsoft.Extensions.Logging.EventSource.dll, /repo/dist/Microsoft.Extensions.Hosting.dll, /repo/dist/Microsoft.Extensions.Options.dll and 28 more · reported by cisco-skill-scanner
31 UNANALYZABLE_BINARY
Files: /repo/dist/Microsoft.Extensions.Configuration.Abstractions.dll, /repo/dist/Microsoft.Extensions.Hosting.dll, /repo/dist/Microsoft.Extensions.Configuration.CommandLine.dll and 28 more · reported by cisco-skill-scanner
2 AAK-SUPPLY-004
Files: package.json, pyproject.toml · reported by agent-audit-kit
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-006
Files: mcp.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: mcp.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/repo/DEPLOYMENT_STRATEGY.md, SECURITY.md, /repo/SKILL.md · reported by cisco-skill-scanner, agent-audit-kit
Critical credential exposure and network egress detected.
A critical finding indicates potential credential exposure within `/repo/screenshot_mcp_server.py`. High severity findings point to additional credential exposure in `/repo/screenshot_mcp_server.py` and `src/index.ts`, alongside network egress capabilities via an SDK in `src/index.ts`. Further medium severity findings identify undeclared network activity and the presence of unanalyzable binaries, which can obscure functionality. These findings collectively suggest the artifact can access sensitive data, communicate externally, and contains opaque components.
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.