Spotify Play Count MCP: Plays & Monthly Listeners
PYPI · SPOTIFY-PLAY-COUNT-MCP · 2 COMPONENTS
Spotify play counts for any track, album, artist or playlist, plus monthly listeners and followers.
Available components
Last scanned (1 day ago)
Scores higher than 59% of PyPI servers
Category Entertainment and Games
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GeminiGeorge22/spotify-play-count-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 482 tokens (~482/item across 1 items; 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 4 Nov 26 63
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 · Analysed pypi/spotify-play-count-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GeminiGeorge22/spotify-play-count-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GeminiGeorge22/spotify-play-count-mcp/.github/workflows/pypi-publish.yml@refs/tags/python-v0.1.0 |
| Rekor log index | 3683206866 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7652b82ccf20f998944522b0c6852136902464567ceaaf4b339b4ff15e18da23 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
publicrecords--spotify-play-count-scraper Spotify Play Count & Monthly Listeners Scraper ~438
Spotify Play Count & Monthly Listeners Scraper. Play counts for every track of any Spotify album, playlist or artist, plus monthly listeners and followers for artists. Optional streams per day for tracked tracks. No login. When to use: Use when you need Spotify play counts: the total plays of every track behind a track, album, artist or playlist link, plus an artist's monthly listeners, followers, world rank and top cities. Optional streams over the last 1, 7 and 30 days for tracks already in daily tracking; those fields stay empty for a track's first day and fill in once it has history. Good for release tracking, playlist checks and artist comparisons; not for private Spotify for Artists data or royalties. Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset. Behavior: starts one run of the Apify Actor "publicrecords/spotify-play-count-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/spotify-play-count-scraper
| Name | Type | Req | Description |
|---|---|---|---|
| addDailyStreams | boolean | – | Adds streams per day for tracks we have been tracking. Tracks seen for the first time get empty values today and history from tomorrow. |
| includeArtistAlbums | boolean | – | Off: an artist link returns the artist row plus its top tracks. On: also every track of the albums and singles shown on the artist page (slower). |
| maxTracksPerTarget | integer | – | 0 means no limit. Large playlists and full catalogs can run to thousands of tracks. |
| urls | array | yes | One per line: track, album, artist or playlist links (open.spotify.com/…) or URIs (spotify:album:…). Example: ["https://open.spotify.com/album/4aawyAB9vmqN3uQ7FjRGTy"] |
No output schema declared.
No examples provided.
How do I install the Spotify Play Count MCP: Plays & Monthly Listeners server?
Spotify Play Count MCP: Plays & Monthly Listeners runs locally as a PyPI package, launched with uvx spotify-play-count-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · spotify-play-count-mcp
claude mcp add geminigeorge22-spotify-play-count-mcp -- uvx spotify-play-count-mcp
What is the Spotify Play Count MCP: Plays & Monthly Listeners server?
Spotify Play Count MCP: Plays & Monthly Listeners is listed in the public MCP registry as io.github.GeminiGeorge22/spotify-play-count-mcp. Spotify play counts for any track, album, artist or playlist, plus monthly listeners and followers. This page covers its PyPI package (spotify-play-count-mcp).
Is the Spotify Play Count MCP: Plays & Monthly Listeners server safe to use?
Spotify Play Count MCP: Plays & Monthly Listeners scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Play Count MCP: Plays & Monthly Listeners server expose?
Spotify Play Count MCP: Plays & Monthly Listeners exposes 1 tool: publicrecords--spotify-play-count-scraper. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.
Is the Spotify Play Count MCP: Plays & Monthly Listeners server still maintained?
Spotify Play Count MCP: Plays & Monthly Listeners 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.
What licence is the Spotify Play Count MCP: Plays & Monthly Listeners server under?
Spotify Play Count MCP: Plays & Monthly Listeners declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.