Spotify Data
REMOTE · SPOTIFY-PROXY.CHECKLEAKED.CC · 2 COMPONENTS
Spotify play counts, monthly listeners, charts, artist stats, albums, playlists and ISRC lookup.
Available components
Last scanned (22 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1637 tokens (~125/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 1430 → 1637 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “fetch” functional
- 1 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://spotify-proxy.checkleaked.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=checkleaked.cc | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 149af537d24e6c3613d7530a5ea8ce3b |
| SANs: checkleaked.cc, *.checkleaked.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spotify-proxy.checkleaked.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| checkleaked.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spotify-proxy.checkleaked.cc/mcp | Verified | 200 | |
| http (plaintext) | http://spotify-proxy.checkleaked.cc/mcp | HTTPS enforced | 301 | https://spotify-proxy.checkleaked.cc/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch Fetch a Spotify record ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | track:<id>, artist:<id>, album:<id> or playlist:<id> from search, a spotify: URI or an open.spotify.com URL. |
No output schema declared.
No examples provided.
get_album Get album ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| album | string | yes | Spotify album id, spotify:album:<id> URI or open.spotify.com/album/<id> URL. |
| include_play_counts | boolean | – | Add each track's lifetime play count and the album total. |
No output schema declared.
No examples provided.
get_artist_insights Artist genres, moods and BPM ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artists | array | yes | Spotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<id> URLs (1-20). |
No output schema declared.
No examples provided.
get_artist_overview Artist overview ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | Spotify artist id, spotify:artist:<id> URI or open.spotify.com/artist/<id> URL. |
| top_tracks | integer | – | How many top tracks to return (1-10). |
No output schema declared.
No examples provided.
get_artists_stats Artist monthly listeners and stats ~74
Monthly listeners, followers, world rank, popularity, genres and top 5 cities (with listener counts) for up to 50 artists in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| artists | array | yes | Spotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<id> URLs (1-50). |
No output schema declared.
No examples provided.
get_chart Spotify charts ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chart | string | – | Which chart. |
| country | string | – | 'global' or a 2-letter country code, e.g. 'us', 'br', 'mx'. |
| date | string | – | 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). |
No output schema declared.
No examples provided.
get_playlist Get playlist ~134
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Spotify playlist id, spotify:playlist:<id> URI or open.spotify.com/playlist/<id> URL. |
No output schema declared.
No examples provided.
get_related_artists Related artists ~70
Artists Spotify lists as related to ("Fans also like") the given artist.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | yes | Spotify artist id, spotify:artist:<id> URI or open.spotify.com/artist/<id> URL. |
| limit | integer | – | How many related artists to return (1-20). |
No output schema declared.
No examples provided.
get_track_insights Track genres, moods and BPM ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tracks | array | yes | Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50). |
No output schema declared.
No examples provided.
get_track_play_count Track play counts ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tracks | array | yes | Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50). |
No output schema declared.
No examples provided.
get_tracks Get tracks ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_insights | boolean | – | Add genres, moods, BPM, credits and languages (slower). |
| include_play_counts | boolean | – | Add each track's lifetime play count. |
| tracks | array | yes | Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50). |
No output schema declared.
No examples provided.
isrc_lookup Find tracks by ISRC ~66
Find the Spotify track(s) for an ISRC (International Standard Recording Code), e.g. USUG11904206. Returns ids, names, artists, album and release date.
| Name | Type | Req | Description |
|---|---|---|---|
| isrc | string | yes | 12-character ISRC; spaces and dashes are ignored. |
No output schema declared.
No examples provided.
search Search Spotify ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_play_counts | boolean | – | Track searches only: add lifetime play counts (slightly slower). |
| limit | integer | – | Number of results (1-20). |
| query | string | yes | Search text, e.g. 'Bad Bunny' or 'blinding lights the weeknd'. |
| type | string | – | What to search for. |
No output schema declared.
No examples provided.
How do I install the Spotify Data MCP server?
Spotify Data is a hosted endpoint at https://spotify-proxy.checkleaked.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · spotify-proxy.checkleaked.cc
claude mcp add --transport http cc-checkleaked-spotify-data 'https://spotify-proxy.checkleaked.cc/mcp'
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 hosted endpoint (https://spotify-proxy.checkleaked.cc/mcp).
Is the Spotify Data MCP server safe to use?
Spotify Data scores 72 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 13 tools: search, fetch, get_tracks, get_track_play_count, get_track_insights, and 8 more. Their descriptions and schemas cost roughly 1,440 tokens of context every time the server is loaded.
Does the Spotify Data MCP server require authentication?
No. We connected to Spotify Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.