# Spotify Data (remote · spotify-proxy.checkleaked.cc)

Spotify play counts, monthly listeners, charts, artist stats, albums, playlists and ISRC lookup.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `spotify-proxy.checkleaked.cc`: 73/100 (this document), [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, [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

- Endpoint: `https://spotify-proxy.checkleaked.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. 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.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http cc-checkleaked-spotify-data 'https://spotify-proxy.checkleaked.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cc-checkleaked-spotify-data": {
      "url": "https://spotify-proxy.checkleaked.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cc-checkleaked-spotify-data": {
      "type": "http",
      "url": "https://spotify-proxy.checkleaked.cc/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cc-checkleaked-spotify-data]
url = "https://spotify-proxy.checkleaked.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-checkleaked-spotify-data": {
      "type": "remote",
      "url": "https://spotify-proxy.checkleaked.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cc-checkleaked-spotify-data --url 'https://spotify-proxy.checkleaked.cc/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cc-checkleaked-spotify-data:
    url: "https://spotify-proxy.checkleaked.cc/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cc-checkleaked-spotify-data": {
      "Transport": "http",
      "Url": "https://spotify-proxy.checkleaked.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cc-checkleaked-spotify-data -t streamable-http -u 'https://spotify-proxy.checkleaked.cc/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cc-checkleaked-spotify-data": {
      "type": "http",
      "url": "https://spotify-proxy.checkleaked.cc/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 72, +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.

### 2026-11-02 (score 71, 0)

- [security] 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
- [functional regression] Schema quality: 1430 → 1637
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “fetch”

### 2026-11-01 (score 71)

First indexed and scored.

## MCP tools (13)

### `search` (~169 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, 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.

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.

### `fetch` (~148 tokens)

Fetch 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.

Input parameters:

- `id` (string, required): track:<id>, artist:<id>, album:<id> or playlist:<id> from search, a spotify: URI or an open.spotify.com URL.

### `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:<id> URIs or open.spotify.com/track/<id> 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:<id> URIs or open.spotify.com/track/<id> 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:<id> URIs or open.spotify.com/track/<id> 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:<id> URIs or open.spotify.com/artist/<id> 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:<id> URI or open.spotify.com/artist/<id> 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:<id> URIs or open.spotify.com/artist/<id> 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:<id> URI or open.spotify.com/artist/<id> 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:<id> URI or open.spotify.com/album/<id> 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:<id> URI or open.spotify.com/playlist/<id> URL.

### `get_chart` (~192 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` (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).

### `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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cc-checkleaked-spotify-data/spotify-proxy#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71

## 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 hosted endpoint (https://spotify-proxy.checkleaked.cc/mcp).

### Is the Spotify Data MCP server safe to use?

Spotify Data scores 73 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://spotify-proxy.checkleaked.cc/mcp
- Authorisation metadata: https://spotify-proxy.checkleaked.cc/.well-known/oauth-protected-resource/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/spotify-proxy.xml
- Changelog JSON feed: https://verifymcp.io/servers/cc-checkleaked-spotify-data/spotify-proxy.json
- HTML version of this page: https://verifymcp.io/servers/cc-checkleaked-spotify-data/spotify-proxy