cc.checkleakedPublished by checkleaked.ccOfficial publisherv0.1.1Updated Nov 1, 2026
Spotify play counts, monthly listeners, charts, artist stats, albums, playlists and ISRC lookup.
Read-only Spotify data server: track play counts, artist listeners and rank, charts, albums, playlists and ISRC lookup, using your own API key.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/cc.checkleaked%2Fspotify-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"spotify-data": {
"type": "http",
"url": "https://spotify-proxy.checkleaked.cc/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}[PyPI] [Python] [License: MIT]
An MCP server that lets AI assistants (Claude Desktop, Claude Code, Cursor, VS Code and other MCP clients) look up Spotify data: track play counts, artist monthly listeners, world rank and top cities, Top 200 and viral charts by country, albums and playlists with per-track play counts, search, ISRC lookup, and genres, moods and BPM.
It runs on your machine and calls the CheckLeaked Spotify Data API with your own API key. A free trial key needs no card. Step-by-step guide: spotify.checkleaked.cc/spotify-mcp-server.
Unofficial. Not affiliated with, endorsed by or sponsored by Spotify. Spotify is a trademark of Spotify AB.
Every user needs their own key. Pick one:
Keys issued by spotify.checkleaked.cc (they start with sapi_) are sent to the direct API
automatically; any other key is treated as a RapidAPI key. Set SPOTIFY_API_PROVIDER only
to override that.
The server is published on PyPI and runs with uvx (part of
uv; install it with pip install uv or see the
uv install guide). uvx
downloads the package into a cached, isolated environment on first use. Replace
your-api-key with your key in the snippets below.
The same 12 tools, plus a fetch tool for ChatGPT, are also hosted at https://spotify-proxy.checkleaked.cc/mcp (Streamable
HTTP). It takes any of the keys above: keys from spotify.checkleaked.cc (they start with sapi_)
are spent on the direct API, and any other key on RapidAPI's spotify81 listing, so a RapidAPI
subscription works too. Add &provider=direct or &provider=rapidapi to the URL to choose.
Claude.ai (Settings → Connectors → Add custom connector) and ChatGPT (Settings →
Connectors; also usable in deep research, which calls its search and fetch tools) cannot
send custom headers, so put the key in the URL:
https://spotify-proxy.checkleaked.cc/mcp?key=your-api-key. Treat that URL like a password.
Clients that can send headers use https://spotify-proxy.checkleaked.cc/mcp with
Authorization: Bearer your-api-key. With Claude Code:
Each tool call spends one request of your key, as a direct API call would.
Edit claude_desktop_config.json (Settings > Developer > Edit Config; macOS:
~/Library/Application Support/Claude/claude_desktop_config.json, Windows:
%APPDATA%\Claude\claude_desktop_config.json) and restart Claude Desktop:
If Claude Desktop cannot find uvx, put its full path in command (run which uvx on
macOS / Linux or where uvx on Windows).
Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
Add to .vscode/mcp.json. VS Code asks for the key once and stores it securely:
Run uvx checkleaked-spotify-mcp (stdio transport) with SPOTIFY_API_KEY in its
environment. Without uvx: pip install checkleaked-spotify-mcp, then run
checkleaked-spotify-mcp (or python -m checkleaked_spotify_mcp).
The same server is published as a container image (linux/amd64 and linux/arm64):
In a client config, use "command": "docker" with
"args": ["run", "-i", "--rm", "-e", "SPOTIFY_API_KEY", "ghcr.io/eduair94/spotify-data-mcp"]
and SPOTIFY_API_KEY under env. Keep -i: the server speaks MCP over stdin and stdout.
Without a key the server still starts, and every tool answers with an error that says where to get a free key, so you can see what is wrong from inside your chat.
All tools are read-only. Every id parameter accepts a bare id, a spotify: URI or an
open.spotify.com URL (with or without /intl-xx/ and ?si=).
Outputs are compact JSON: ids, names, numbers and open.spotify.com URLs, with lists capped,
so they fit in the model's context. Notes:
streams are the plays in that chart's day or week.The server only talks to the API you configure (RapidAPI's spotify81.p.rapidapi.com or
spotify-proxy.checkleaked.cc). It sends your key in the x-rapidapi-key header, stores
nothing on disk and has no telemetry. Requests carry a checkleaked-spotify-mcp/<version>
user agent.
The hosted server passes each tool call to the same API with your key and keeps no
conversation data. A key sent in the URL can appear in request logs like any URL, so prefer
the Authorization header where your client supports it.
Built on the official MCP Python SDK
and the checkleaked-spotify-api SDK.
API reference: spotify-proxy.checkleaked.cc/docs.
Service status: spotify.checkleaked.cc/status.
Source: README.md at commit fbca604
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, plus `results` (id such as track:<id>, title, url) for the fetch tool. For track searches, include_play_counts adds each hit's lifetime play count.
typelimitqueryrequiredinclude_play_countsFetch a Spotify record
The full record behind a search result: a track (play count, album, release date, genres, moods, BPM, credits), an artist (monthly listeners, followers, world rank, top cities, top tracks), an album (every track with play counts) or a playlist (details and its first 50 tracks with play counts). Takes an id from the search results (track:<id>, artist:<id>, album:<id>, playlist:<id>), a spotify: URI or an open.spotify.com URL.
idrequiredGet 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.
tracksrequiredinclude_insightsinclude_play_countsTrack 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.
tracksrequiredTrack 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.
tracksrequiredArtist 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.
artistsrequiredArtist 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.
artistrequiredtop_tracksArtist 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.
artistsrequiredRelated artists
Artists Spotify lists as related to ("Fans also like") the given artist.
limitartistrequiredGet 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.
albumrequiredinclude_play_countsGet 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).
limitoffsetplaylistrequiredinclude_play_countsSpotify 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.
datechartlimitperiodcountryinclude_play_countsFind 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.
isrcrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
uvx checkleaked-spotify-mcp# or, with Dockerdocker run -i --rm -e SPOTIFY_API_KEY=your-api-key ghcr.io/eduair94/spotify-data-mcpclaude mcp add --transport http spotify-data https://spotify-proxy.checkleaked.cc/mcp --header "Authorization: Bearer your-api-key"{ "mcpServers": { "spotify-data": { "command": "uvx", "args": ["checkleaked-spotify-mcp"], "env": { "SPOTIFY_API_KEY": "your-api-key" } } }}claude mcp add spotify-data -s user -e SPOTIFY_API_KEY=your-api-key -- uvx checkleaked-spotify-mcp{ "mcpServers": { "spotify-data": { "command": "uvx", "args": ["checkleaked-spotify-mcp"], "env": { "SPOTIFY_API_KEY": "your-api-key" } } }}{ "inputs": [ { "type": "promptString", "id": "spotify-api-key", "description": "Spotify Data API key", "password": true } ], "servers": { "spotify-data": { "type": "stdio", "command": "uvx", "args": ["checkleaked-spotify-mcp"], "env": { "SPOTIFY_API_KEY": "${input:spotify-api-key}" } } }}docker run -i --rm -e SPOTIFY_API_KEY=your-api-key ghcr.io/eduair94/spotify-data-mcpgit clone https://github.com/eduair94/spotify-data-mcpcd spotify-data-mcppython -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activatepip install -e ".[dev]"pytest # offline tests (recorded API answers)SPOTIFY_MCP_LIVE=1 SPOTIFY_API_KEY=... pytest -m live # optional live smoke test