Spotify (obrien-matthew) MCP Server
mcp-spotify
PyPI
v0.2.1
Published by obrien-matthew — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Spotify playlist building and playback control
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Hardcoded egress to an external endpoint (src/spotify_mcp/client.py)MTC-SRC-003
In the server's implementation (`src/spotify_mcp/client.py:142`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: lse) resp = requests.post( "https://api.spotify.com/v1/me/playlists", header
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/spotify_mcp/client.py
Tools 20
Each tool and what it can reach — statically extracted from the published source.
add_to_queueno sensitive capabilityadd_tracks_to_playlistno sensitive capabilitycreate_playlistno sensitive capabilityfollow_playlistno sensitive capabilityget_album_tracksno sensitive capabilityget_my_playlistsno sensitive capabilityget_my_top_artistsno sensitive capabilityget_my_top_tracksno sensitive capabilityget_now_playingno sensitive capabilityget_playlist_tracksno sensitive capability
Show 10 more tools ↓
get_saved_tracksno sensitive capabilityget_server_versionno sensitive capabilitypause_playbackno sensitive capabilityplay_trackno sensitive capabilityremove_tracks_from_playlistno sensitive capabilityreplace_playlist_tracksno sensitive capabilitysearch_albumsno sensitive capabilitysearch_artistsno sensitive capabilitysearch_tracksno sensitive capabilityunfollow_playlistno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.1 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-01 |
v0.2.0 |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-spotify --online --registry pypiOther implementations of Spotify 8
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
Model Context Protocol server for Spotify integration
MCP spotify project
MCP server for the Spotify Web API — use Claude to manage playlists, control playback, and get recommendations
Production-ready MCP server for Spotify control with bulletproof error handling
Spotify Web API MCP server for accessing music, artists, albums, and recommendations
Spotify MCP Server for Claude and other AI assistants
More in Design & Media
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Aleph's official SiliconFlow media-generation MCP server (image / video / TTS)
MCP server for image generation using Google Gemini AI
Ambience AI MCP Server - Generate images, videos, and audio through Model Context Protocol
MCP server exposing every endpoint of the AstroWay Calculation API as tools — natal, synastry, transits, Vedic dashas, Tarot, Numerology, Human Design, AI horoscopes — for Claude Desktop, Cursor and any MCP-compatible AI agent.
Audio-guide and trip-planning tools for 1,100+ cities from Audiala. Free, no API key.