Loading the registry…
A Model Context Protocol server for NBA player statistics from basketball-reference.com
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.
1 critical finding 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 -- nba-player-stats-mcp
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.
v2.0.11
3 findings · 6.0s
v0.3.74
3 findings · 1.4s
v0.1.0
0 findings · 2.6s
v0.1.0
0 findings · 2.6s
v2.3.8
18 findings · 1.1s
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.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.6s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.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 | Flagged48 | — | 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 ·n/a: not applicableosv-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 24 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
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.
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 FILE_MAGIC_MISMATCH
Files: /repo/requirements.txt · reported by cisco-skill-scanner
1 GHSA-c2jp-c369-7pvx
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-rcfx-77hg-w2wv
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2020-62
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2020-73
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2021-19
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2021-852
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2022-230
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-74
Files: /repo/requirements.txt · reported by osv-scanner
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-1872
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements.txt · 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-338
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-87
Files: /repo/requirements.txt · reported by osv-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-ATTEST-001, AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: mcp-config-example.json, SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical and high vulnerabilities found in artifact dependencies.
The artifact contains a critical vulnerability (PYSEC-2026-338) and several high-severity vulnerabilities in its dependencies, as listed in `/repo/requirements.txt`. These vulnerabilities could potentially allow for remote code execution, denial of service, or unauthorized information access. Further investigation into the specific impact of these dependency issues is recommended.
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.