Loading the registry…
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 -- play-mcp
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.
v2.0.11
6 findings · 8.9s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged64 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable |
v0.3.74
0 findings · 3.0s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
vv0.3.2
Incomplete run
0 findings · 3.2s
v0.71.0
12 findings · 0.2s
v2.3.8
61 findings · 0.8s
vv1.6.0
Incomplete run
0 findings · 2.0s
v1.4.0
None of the entry points this scanner reads 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 · 1.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
| 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 79 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 74 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.
1 GO-2026-4865
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5030
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/go.mod · reported by osv-scanner
74 The model's answer could not be read.
Rules: CVE-2026-39821, CVE-2026-33814, CVE-2026-46600 and 68 more · Files: go.mod, /repo/go.mod, /repo/bin/mcp-server and 1 more · reported by trivy, osv-scanner, cisco-skill-scanner
High severity findings indicate potential for data exposure and system compromise.
The artifact contains high severity findings related to sensitive data handling in `/repo/internal/server/server.go` and `/repo/pkg/scraper/homes.go`, which could lead to network egress of sensitive information. Additionally, several high severity vulnerabilities (CVEs) are present in dependencies listed in `go.mod`. These vulnerabilities could enable various impacts, including remote code execution or further system compromise.
Concern level assessed by the review: High. 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.