# Spotify Data (oci · ghcr.io/eduair94/spotify-data-mcp) Spotify play counts, monthly listeners, charts, artist stats, albums, playlists and ISRC lookup. - Trust score: 42/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `spotify-proxy.checkleaked.cc`: 73/100, [markdown](https://verifymcp.io/servers/cc-checkleaked-spotify-data/spotify-proxy.md), [page](https://verifymcp.io/servers/cc-checkleaked-spotify-data/spotify-proxy) - oci · `ghcr.io/eduair94/spotify-data-mcp`: 42/100 (this document), [markdown](https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp.md), [page](https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp) ## Channel facts - Registry: `oci` - Package: `ghcr.io/eduair94/spotify-data-mcp` - Version: `0.1.1` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 3 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 75/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1428 tokens (~119/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 13/100 - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Spotify Data MCP server? Spotify Data runs locally as a container image, launched with docker run --rm -i -e SPOTIFY_API_KEY -e SPOTIFY_API_PROVIDER ghcr.io/eduair94/spotify-data-mcp:0.1.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add cc-checkleaked-spotify-data -- docker run --rm -i -e SPOTIFY_API_KEY -e SPOTIFY_API_PROVIDER ghcr.io/eduair94/spotify-data-mcp:0.1.1 ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Cursor ```json { "mcpServers": { "cc-checkleaked-spotify-data": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1" ] } } } ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### VS Code ```json { "servers": { "cc-checkleaked-spotify-data": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1" ] } } } ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Codex ```bash codex mcp add cc-checkleaked-spotify-data -- docker run --rm -i -e SPOTIFY_API_KEY -e SPOTIFY_API_PROVIDER ghcr.io/eduair94/spotify-data-mcp:0.1.1 ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cc-checkleaked-spotify-data": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1" ], "enabled": true } } } ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Hermes ```yaml mcp_servers: cc-checkleaked-spotify-data: command: "docker" args: ["run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1"] ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Netclaw ```json { "McpServers": { "cc-checkleaked-spotify-data": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1" ] } } } ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Other ```json { "mcpServers": { "cc-checkleaked-spotify-data": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SPOTIFY_API_KEY", "-e", "SPOTIFY_API_PROVIDER", "ghcr.io/eduair94/spotify-data-mcp:0.1.1" ] } } } ``` This image reads SPOTIFY_API_KEY and SPOTIFY_API_PROVIDER. Set them in your client's env block for this server; docker run -e passes each one through to the container. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 42, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 41) First indexed and scored. ## MCP tools (12) ### `search` (~148 tokens) Search Spotify Search the Spotify catalog by name to find ids for the other tools. `type` picks what to search: tracks, artists, albums or playlists. Returns up to `limit` hits (max 20) with id, name, key fields and open.spotify.com URL. For track searches, include_play_counts adds each hit's lifetime play count. Input parameters: - `include_play_counts` (boolean): Track searches only: add lifetime play counts (slightly slower). - `limit` (integer): Number of results (1-20). - `query` (string, required): Search text, e.g. 'Bad Bunny' or 'blinding lights the weeknd'. - `type` (string): What to search for. ### `get_tracks` (~152 tokens) Get tracks Track details for up to 50 tracks in one call: name, artists, album, release date, duration, explicit flag, popularity, ISRC and (by default) lifetime play count. include_insights adds genres, moods, activities, BPM, credits, lyrics flag and languages. A play count of 0 means fewer than 1,000 plays. Input parameters: - `include_insights` (boolean): Add genres, moods, BPM, credits and languages (slower). - `include_play_counts` (boolean): Add each track's lifetime play count. - `tracks` (array, required): Spotify track ids, spotify:track: URIs or open.spotify.com/track/ URLs (1-50). ### `get_track_play_count` (~91 tokens) Track play counts Lifetime Spotify play counts (streams) for up to 50 tracks in one call, with track name, artists and release date. The fastest way to compare streams. A play count of 0 means fewer than 1,000 plays. Input parameters: - `tracks` (array, required): Spotify track ids, spotify:track: URIs or open.spotify.com/track/ URLs (1-50). ### `get_track_insights` (~80 tokens) Track genres, moods and BPM Genres, moods and activities (with Spotify's 0-1 weights), tempo in BPM, credits (writers, producers), lyrics flag and vocal languages for up to 50 tracks. Input parameters: - `tracks` (array, required): Spotify track ids, spotify:track: URIs or open.spotify.com/track/ URLs (1-50). ### `get_artists_stats` (~74 tokens) Artist monthly listeners and stats Monthly listeners, followers, world rank, popularity, genres and top 5 cities (with listener counts) for up to 50 artists in one call. Input parameters: - `artists` (array, required): Spotify artist ids, spotify:artist: URIs or open.spotify.com/artist/ URLs (1-50). ### `get_artist_overview` (~93 tokens) Artist overview One artist's profile: monthly listeners, followers, world rank, top cities, top tracks with play counts, latest release, discography counts, related artists, biography and social links. Input parameters: - `artist` (string, required): Spotify artist id, spotify:artist: URI or open.spotify.com/artist/ URL. - `top_tracks` (integer): How many top tracks to return (1-10). ### `get_artist_insights` (~83 tokens) Artist genres, moods and BPM An artist's sound profile from their top tracks: genres, moods and activities with 0-1 weights, and tempo (average, min, max BPM). Up to 20 artists per call. Input parameters: - `artists` (array, required): Spotify artist ids, spotify:artist: URIs or open.spotify.com/artist/ URLs (1-20). ### `get_related_artists` (~70 tokens) Related artists Artists Spotify lists as related to ("Fans also like") the given artist. Input parameters: - `artist` (string, required): Spotify artist id, spotify:artist: URI or open.spotify.com/artist/ URL. - `limit` (integer): How many related artists to return (1-20). ### `get_album` (~88 tokens) Get album An album with its track list and (by default) every track's lifetime play count, plus the album total, release date, label, UPC and popularity. Input parameters: - `album` (string, required): Spotify album id, spotify:album: URI or open.spotify.com/album/ URL. - `include_play_counts` (boolean): Add each track's lifetime play count and the album total. ### `get_playlist` (~134 tokens) Get playlist A playlist's name, owner, followers and description, plus `limit` tracks (max 100) from `offset` with lifetime play counts. Use next_offset from the answer to page through long playlists (later pages skip the metadata and cost one request). Input parameters: - `include_play_counts` (boolean): Add each track's lifetime play count. - `limit` (integer): Tracks to return (1-100). - `offset` (integer): Index of the first track (0 = start). - `playlist` (string, required): Spotify playlist id, spotify:playlist: URI or open.spotify.com/playlist/ URL. ### `get_chart` (~190 tokens) Spotify charts Spotify Charts by country: top_tracks (Top 200), viral_tracks (Viral 50, daily only), top_artists or top_albums. Each entry has rank, previous and peak rank, days (or weeks) on the chart, movement and, for top_tracks, the streams in that period. Defaults to the latest published daily chart. Input parameters: - `chart` (string): Which chart. - `country` (string): 'global' or a 2-letter country code, e.g. 'us', 'br', 'mx'. - `date`: Chart date YYYY-MM-DD; omit for the latest published chart. - `include_play_counts` (boolean): top_tracks / viral_tracks: add each track's lifetime play count (slower). - `limit` (integer): Entries to return (1-200). - `period` (string): Daily or weekly chart (viral_tracks is daily only). ### `isrc_lookup` (~66 tokens) Find tracks by ISRC Find the Spotify track(s) for an ISRC (International Standard Recording Code), e.g. USUG11904206. Returns ids, names, artists, album and release date. Input parameters: - `isrc` (string, required): 12-character ISRC; spaces and dashes are ignored. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp#diagnostics ## Score history - 2026-11-05: 42 - 2026-11-04: 42 - 2026-11-03: 41 - 2026-11-02: 41 - 2026-11-01: 41 ## Common questions ### What is the Spotify Data MCP server? Spotify Data is an MCP server listed in the public MCP registry as cc.checkleaked/spotify-data. Spotify play counts, monthly listeners, charts, artist stats, albums, playlists and ISRC lookup. This page covers its container image (ghcr.io/eduair94/spotify-data-mcp). ### Is the Spotify Data MCP server safe to use? Spotify Data scores 42 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Spotify Data MCP server expose? Spotify Data exposes 12 tools: search, get_tracks, get_track_play_count, get_track_insights, get_artists_stats, and 7 more. Their descriptions and schemas cost roughly 1,269 tokens of context every time the server is loaded. ### Is the Spotify Data MCP server still maintained? Spotify Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the Spotify Data MCP server under? Spotify Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ### What did VerifyMCP test on the Spotify Data MCP server? VerifyMCP ran 12 checks on Spotify Data, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Spotify Data: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - GitHub Container Registry: https://ghcr.io/eduair94/spotify-data-mcp - Repository: https://github.com/eduair94/spotify-data-mcp - Website: https://spotify.checkleaked.cc/ - Changelog RSS feed: https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp/changelog.json - Trust report (JSON): https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp.json - HTML version of this page: https://verifymcp.io/servers/cc-checkleaked-spotify-data/ghcr-io-eduair94-spotify-data-mcp