The MCP ecosystem often has several independent packages implementing the same tool — and "Spotify" currently has 8. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.
| Implementation | Package | Trust | Capability | Coverage | Findings | Scanned |
|---|---|---|---|---|---|---|
| Spotifybest by thomaswawra | @thomaswawra/server-spotify
npm |
A 100/100 | Moderate | Source | 1 | 2026-07-22 |
| Spotify by xavifabregat | @xavifabregat/spotify-mcp
npm |
A 100/100 | High | Source | 1 | 2026-07-22 |
| Spotify by calebWei | spotify-mcp
npm |
A 100/100 | Moderate | Source | 2 | 2026-07-22 |
| Spotify by tbrgeek | @tbrgeek/spotify-mcp-server
npm |
A 100/100 | Moderate | Source | 2 | 2026-07-22 |
| Spotify by PyPI | spotify-mcp
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Spotify by nlevy | spotify-mcp-server
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Spotify by PyPI | mcp-server-spotify
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Spotify by obrien-matthew | mcp-spotify
PyPI |
A 98/100 | Moderate | Source | 2 | 2026-07-22 |
A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.