Loading the registry…
专业图片处理 MCP 服务器
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 osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- ps-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
6 findings · 10.4s
v0.3.74
8 findings · 5.8s
v0.1.0
0 findings · 4.9s
v0.1.0
3 findings · 4.9s
v0.71.0
39 findings · 0.3s
v2.3.8
67 findings · 1.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.2s
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 | Flagged35 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: 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 123 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 91 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.
1 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 AAK-OAUTH-3P-001
Files: pyproject.toml, requirements.txt · reported by agent-audit-kit
2 PYSEC-2026-165
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1845
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2257
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2874
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3494
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
1 CVE-2026-25990
Files: uv.lock · reported by trivy
1
90 The model's answer could not be read.
Rules: PYSEC-2026-457, PYSEC-2026-2120, AAK-MCP-SDK-CVE-2026-52869-001 and 69 more · Files: /repo/requirements.txt, /repo/uv.lock, pyproject.toml and 8 more · reported by osv-scanner, agent-audit-kit, trivy and 2 more
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell · Files: /repo/README.md · reported by nerlo-install-instruction
Critical vulnerabilities and high-risk capabilities detected.
The artifact contains critical vulnerabilities, including PYSEC-2026-457 and PYSEC-2026-2120, which warrant immediate attention. Multiple high-severity vulnerabilities are also present, some of which relate to potential DNS rebinding and SDK issues. The artifact's installed code includes components with known vulnerabilities that could lead to various security compromises.
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.
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-42308
Files: uv.lock · reported by trivy
1 CVE-2026-42309
Files: uv.lock · reported by trivy
1 CVE-2026-42310
Files: uv.lock · reported by trivy
1 CVE-2026-42561
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-59199
Files: uv.lock · reported by trivy
1 CVE-2026-59200
Files: uv.lock · reported by trivy
1 CVE-2026-59204
Files: uv.lock · reported by trivy
1 PYSEC-2023-183
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1794
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1852
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
Showing 23 of 23; the rest are in the per-scanner reports above.