Loading the registry…
Control your Spotify music from Claude using the MCP protocol
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 -- mcp-spotify-player
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
19 findings · 6.4s
v0.3.74
9 findings · 2.9s
v0.2.0
7 findings · 3.5s
v0.2.0
0 findings · 3.5s
v2.3.8
14 findings · 1.2s
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 · 2.1s
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
7 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged31 | — | 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 |
| Jul 30, 2026 | Flagged26 | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner: completetrivy_image ·n/a: not applicable | completed |
| Jul 21, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 49 findings across every scanner that examined this package.
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.
6 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: YARA_prompt_injection_unicode_steganography, OVERSIZED_FILE · Files: /repo/docs/media/hero.gif · reported by cisco-skill-scanner
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-SECRET-004, DATA_EXFIL_NETWORK_REQUESTS · Files: tests/test_error_mapping.py, /repo/tests/auth/test_callback_html.py, /repo/tests/auth/test_ensure_tokens_flow.py · reported by agent-audit-kit, cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
7 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/src/mcp_spotify/auth/tokens.py, /repo/src/mcp_spotify_player/client_auth.py, /repo/src/mcp_spotify_player/spotify_client.py · reported by cisco-skill-scanner
7 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/src/mcp_spotify/auth/tokens.py, /repo/src/mcp_spotify_player/client_auth.py, /repo/src/mcp_spotify_player/spotify_client.py · reported by nerlo-behavioral
3 AAK-OAUTH-007
Files: src/mcp_spotify_player/client_auth.py, src/mcp_spotify_player/config.py, src/mcp_spotify/auth/tokens.py · reported by agent-audit-kit
1 AAK-OAUTH-006
Files: src/mcp_spotify_player/client_auth.py · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-004
Artifact has high-severity vulnerabilities and credential exposure leading to network egress.
The artifact contains multiple high-severity vulnerabilities in its dependencies, which could lead to various security compromises. Additionally, it exposes credentials in `src/mcp_spotify_player/client_auth.py` and `src/mcp_spotify/auth/tokens.py`. These exposed credentials are then used for network egress in `src/mcp_spotify_player/client_auth.py` and `src/mcp_spotify_player/spotify_client.py`, potentially allowing unauthorized data transmission.
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.
Files: src/mcp_spotify_player/client_auth.py · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 DATA_EXFIL_SOCKET_CONNECT
Files: /repo/src/mcp_spotify_player/client_auth.py · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2024-38
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1850
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1851
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1852
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-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/requirements.txt · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/CONTRIBUTING.md · reported by cisco-skill-scanner