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.
npx agentmods add mcp/jamiew/spotify-mcp/spotify-mcpgit 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-mcp)<a href="https://agentmods.dev/mcp/jamiew/spotify-mcp/spotify-mcp"><img src="https://agentmods.dev/badge/mcp/jamiew/spotify-mcp/spotify-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
spotify-mcp 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 5d 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-mcp": {
"command": "uvx",
"args": [
"spotify-mcp-jamiew"
],
"env": {
"SPOTIFY_CLIENT_ID": "",
"SPOTIFY_CLIENT_SECRET": "",
"SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8888"
}
}
}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.
- 5d ago First seen · 13 lines scan A 4c8aa1caadaf
spotify-mcp is an MCP server published in the GitHub repository jamiew/spotify-mcp (9 stars, last pushed 1mo 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-mcp-server
The most complete Spotify MCP: playback, library, playlists, search, podcasts and audiobooks. Runs locally from the @novalux12/spotify-mcp npm package. Needs 1 environment variable to run.
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.
mcp-spotify
MCP server for Spotify playlist building and playback control. Runs locally from the mcp-spotify Python package.
spotify-llm-mcp
MCP server "spotify-llm-mcp" as configured in rachittshah/spotify-llm-mcp. Runs locally from the spotify-llm-mcp Python package.