Loading the registry…
MCP server for Spotify
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.
9 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
pypi: spotify-mcp-server @ 0.1.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- spotify-mcp-server
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
4 findings · 13.8s
v0.3.74
7 findings · 1.9s
v0.1.0
0 findings · 6.6s
v0.1.0
0 findings · 6.6s
v0.1.0
0 findings · 10.5s
v0.71.0
158 findings · 0.6s
v2.3.8
162 findings · 2.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.4s
vv0.3.2
No Go packages were 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 19, 2026 | Flagged42 | — | 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 331 findings across every scanner that examined this package. None of the 9 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 171 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.
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 AAK-SECRET-004
Files: app/auth/oauth.py · reported by agent-audit-kit
2 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-c2jp-c369-7pvx
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 CVE-2025-14009
Files: uv.lock · reported by trivy
1 CVE-2025-59420
Files: uv.lock · reported by trivy
1 CVE-2025-61920
Files: uv.lock · reported by trivy
1 CVE-2025-62708
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-66416
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: uv.lock · reported by trivy
1 CVE-2025-69223
Files: uv.lock · reported by trivy
1 CVE-2025-69229
Files: uv.lock · reported by trivy
1 CVE-2025-71408
Files: uv.lock · reported by trivy
1 CVE-2026-0846
Files: uv.lock · reported by trivy
1 CVE-2026-0847
Files: uv.lock · reported by trivy
1 CVE-2026-12061
Files: uv.lock · reported by trivy
1 CVE-2026-12072
Files: uv.lock · reported by trivy
1 CVE-2026-12074
Files: uv.lock · reported by trivy
1 CVE-2026-12075
Files: uv.lock · reported by trivy
1 CVE-2026-12243
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-25990
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-27124
Files: uv.lock · reported by trivy
1 CVE-2026-27888
Files: uv.lock · reported by trivy
1 CVE-2026-27962
Files: uv.lock · reported by trivy
1 CVE-2026-28351
Files: uv.lock · reported by trivy
1 CVE-2026-28490
Files: uv.lock · reported by trivy
1 CVE-2026-28498
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: uv.lock · reported by trivy
1 CVE-2026-33123
Files: uv.lock · reported by trivy
1 CVE-2026-33231
Files: uv.lock · reported by trivy
1 CVE-2026-33236
Files: uv.lock · reported by trivy
1 CVE-2026-40192
Files: uv.lock · reported by trivy
1 CVE-2026-41314
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-42311
Files: uv.lock · reported by trivy
1 CVE-2026-42561
Files: uv.lock · reported by trivy
1 CVE-2026-44209
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-48156
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-49461
Files: uv.lock · reported by trivy
1 CVE-2026-49476
Files: uv.lock · reported by trivy
1 CVE-2026-49477
Files: uv.lock · reported by trivy
1 CVE-2026-52869
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-54058
Files: uv.lock · reported by trivy
1 CVE-2026-54059
Files: uv.lock · reported by trivy
1 CVE-2026-54060
Files: uv.lock · reported by trivy
1 CVE-2026-54276
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-54293
Files: uv.lock · reported by trivy
1 CVE-2026-54651
Files: uv.lock · reported by trivy
1 CVE-2026-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-59197
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 CVE-2026-59205
Files: uv.lock · reported by trivy
1 CVE-2026-59935
Files: uv.lock · reported by trivy
1 CVE-2026-59936
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 GHSA-rcfx-77hg-w2wv
Files: uv.lock · reported by trivy
1 PYSEC-2026-1101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1200
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1203
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2078
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2085
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2116
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2117
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2236
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2390
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2474
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3004
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3009
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3015
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3020
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3071
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
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
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3581
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3657
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-597
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-96
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-97
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-98
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-99
Files: /repo/uv.lock · reported by osv-scanner
170 The review budget for this scan was already spent before these findings were reached.
Rules: PYSEC-2026-2475, CVE-2025-62707, CVE-2026-33699 and 165 more · Files: /repo/uv.lock, uv.lock, app/auth/oauth.py and 3 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK · Files: /repo/repo/README.md · reported by cisco-skill-scanner
Critical vulnerabilities and exposed secrets detected.
The artifact contains multiple critical vulnerabilities in its dependencies, primarily identified in `uv.lock` and `pyproject.toml`. Additionally, secrets are exposed within the `app/auth/oauth.py` file. These issues could lead to credential access, unauthorized operations, or compromise of the artifact's integrity.
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.
Showing 24 of 24; the rest are in the per-scanner reports above.