_ registry / mcp streamable-http · checked 54m ago

spotify-data

https://spotify-proxy.checkleaked.cc

Registry code: 1d148e7821834829

api record

Read-only Spotify catalog data from the CheckLeaked Spotify Data API: track play counts, artist monthly listeners, followers, world rank and top cities, Top 200 and viral charts, search, albums, playlists, ISRC lookup, and genres / moods / BPM.

- Every tool accepts Spotify ids, spotify: URIs and open.spotify.com URLs. With only a name, call `search` first to get the id.

endpoint
https://spotify-proxy.checkleaked.cc/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is spotify-data live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is spotify-data free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does spotify-data have?
12 tools: get_related_artists, get_playlist, isrc_lookup, search, get_tracks, get_track_play_count, get_track_insights, get_artists_stats, ….
Is spotify-data safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
385ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
1 auth-required 11 never probed 1 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_chart auth-required 54m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "date": {
          "type": "string",
          "description": "Chart date YYYY-MM-DD; omit for the latest published chart."
        },
        "chart": {
          "enum": [
            "top_tracks",
            "viral_tracks",
            "top_artists",
            "top_albums"
          ],
          "type": "string",
          "default": "top_tracks",
          "description": "Which chart."
        },
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 200,
          "minimum": 1,
          "description": "Entries to return (1-200)."
        },
        "period": {
          "enum": [
            "daily",
            "weekly"
          ],
          "type": "string",
          "default": "daily",
          "description": "Daily or weekly chart (viral_tracks is daily only)."
        },
        "country": {
          "type": "string",
          "default": "global",
          "description": "'global' or a 2-letter country code, e.g. 'us', 'br', 'mx'."
        },
        "include_play_counts": {
          "type": "boolean",
          "default": false,
          "description": "top_tracks / viral_tracks: add each track's lifetime play count (slower)."
        }
      }
    }
    arguments 46 lines
  • get_related_artists unknown never probed

    Artists Spotify lists as related to ("Fans also like") the given artist.

    mcp-tool

    {
      "type": "object",
      "required": [
        "artist"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 20,
          "minimum": 1,
          "description": "How many related artists to return (1-20)."
        },
        "artist": {
          "type": "string",
          "minLength": 1,
          "description": "Spotify artist id, spotify:artist:<id> URI or open.spotify.com/artist/<id> URL."
        }
      }
    }
    arguments 20 lines
  • get_playlist unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "playlist"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 100,
          "minimum": 1,
          "description": "Tracks to return (1-100)."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Index of the first track (0 = start)."
        },
        "playlist": {
          "type": "string",
          "minLength": 1,
          "description": "Spotify playlist id, spotify:playlist:<id> URI or open.spotify.com/playlist/<id> URL."
        },
        "include_play_counts": {
          "type": "boolean",
          "default": true,
          "description": "Add each track's lifetime play count."
        }
      }
    }
    arguments 31 lines
  • isrc_lookup unknown never probed

    Find the Spotify track(s) for an ISRC (International Standard Recording Code), e.g. USUG11904206. Returns ids, names, artists, album and release date.

    mcp-tool

    {
      "type": "object",
      "required": [
        "isrc"
      ],
      "properties": {
        "isrc": {
          "type": "string",
          "maxLength": 20,
          "minLength": 12,
          "description": "12-character ISRC; spaces and dashes are ignored."
        }
      }
    }
    arguments 14 lines
  • search unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "tracks",
            "artists",
            "albums",
            "playlists"
          ],
          "type": "string",
          "default": "tracks",
          "description": "What to search for."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "Number of results (1-20)."
        },
        "query": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Search text, e.g. 'Bad Bunny' or 'blinding lights the weeknd'."
        },
        "include_play_counts": {
          "type": "boolean",
          "default": false,
          "description": "Track searches only: add lifetime play counts (slightly slower)."
        }
      }
    }
    arguments 37 lines
  • get_tracks unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tracks"
      ],
      "properties": {
        "tracks": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50)."
        },
        "include_insights": {
          "type": "boolean",
          "default": false,
          "description": "Add genres, moods, BPM, credits and languages (slower)."
        },
        "include_play_counts": {
          "type": "boolean",
          "default": true,
          "description": "Add each track's lifetime play count."
        }
      }
    }
    arguments 27 lines
  • get_track_play_count unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tracks"
      ],
      "properties": {
        "tracks": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50)."
        }
      }
    }
    arguments 17 lines
  • get_track_insights unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tracks"
      ],
      "properties": {
        "tracks": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Spotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50)."
        }
      }
    }
    arguments 17 lines
  • get_artists_stats unknown never probed

    Monthly listeners, followers, world rank, popularity, genres and top 5 cities (with listener counts) for up to 50 artists in one call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "artists"
      ],
      "properties": {
        "artists": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Spotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<id> URLs (1-50)."
        }
      }
    }
    arguments 17 lines
  • get_artist_overview unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "artist"
      ],
      "properties": {
        "artist": {
          "type": "string",
          "minLength": 1,
          "description": "Spotify artist id, spotify:artist:<id> URI or open.spotify.com/artist/<id> URL."
        },
        "top_tracks": {
          "type": "integer",
          "default": 10,
          "maximum": 10,
          "minimum": 1,
          "description": "How many top tracks to return (1-10)."
        }
      }
    }
    arguments 20 lines
  • get_album unknown 54m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "album"
      ],
      "properties": {
        "album": {
          "type": "string",
          "minLength": 1,
          "description": "Spotify album id, spotify:album:<id> URI or open.spotify.com/album/<id> URL."
        },
        "include_play_counts": {
          "type": "boolean",
          "default": true,
          "description": "Add each track's lifetime play count and the album total."
        }
      }
    }
    arguments 18 lines
  • get_artist_insights unknown 54m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "artists"
      ],
      "properties": {
        "artists": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "Spotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<id> URLs (1-20)."
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1d148e7821834829.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1d148e7821834829/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1d148e7821834829/badge.svg)](https://brick.blue/agent/1d148e7821834829?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.