Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/jamiew/spotify-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jamiew/spotify-mcp/spotify)<a href="https://agentmods.dev/mcp/jamiew/spotify-mcp/spotify"><img src="https://agentmods.dev/badge/mcp/jamiew/spotify-mcp/spotify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jamiew/spotify-mcp/spotify"><img src="https://agentmods.dev/badge/mcp/jamiew/spotify-mcp/spotify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
spotify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"spotify": {
"command": "uv",
"args": [
"--directory",
"${CLAUDE_PROJECT_DIR:-.}",
"run",
"spotify-mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A 5a3bc0fdbb27
spotify is an MCP server published in the GitHub repository jamiew/spotify-mcp (12 stars, last pushed 28d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other mcp servers, from other repositories
spotatui
MCP server "spotatui" as configured in LargeModGames/spotatui. Launched with spotatui mcp.
spotify-bulk-actions-mcp
MCP server for bulk Spotify operations with confidence-scored song matching, batch playlist creation, and library exports. Runs locally from the spotify-bulk-actions-mcp Python package. Needs 2 environment variables to run.
spotify-mcp
MCP server "spotify-mcp" as configured in martin-gomola/spotify-mcp. Launched with bash -lc repo="${SPOTIFY_MCP_REPO:-$HOME/dev/spotify-mcp}"; cd "$repo" 2>/dev/nu.
spotify-mcp-server
Spotify Web API MCP: playback, library, playlists, search, podcasts. Not affiliated with Spotify. Runs locally from the @novalux12/spotify-mcp npm package. Needs 1 environment variable to run.
spotify
Spotify MCP — Web API via clientcredentials OAuth. Remote server at gateway.pipeworx.io.
mcp-spotify
MCP server for Spotify playlist building and playback control. Runs locally from the mcp-spotify Python package.