Analyze chess positions and get best moves from UCI engines such as Stockfish or Leela
Spotifyscraper is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
Public Spotify metadata, lyrics and podcasts for LLM agents. No API key, read-only.
Quickstart
# 1 — run it from where its publisher ships it
uvx spotifyscraper
# 2 — ask your agent something
> Public Spotify metadata, lyrics and podcasts for LLM agents. No API key, read-only.
Spotifyscraper is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Spotifyscraper as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add spotifyscraper-mcp -- uvx spotifyscraperReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take SPOTIFY_SP_DC if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Fetch a track by URL, URI, or 22-character ID.
No parameter schema on file.
Fetch an album (with its tracks) by URL, URI, or ID.
No parameter schema on file.
Fetch an artist by URL, URI, or ID.
No parameter schema on file.
Fetch a playlist by URL, URI, or ID (up to ``max_tracks`` tracks).
No parameter schema on file.
Fetch a podcast episode by URL, URI, or ID.
No parameter schema on file.
Fetch a podcast show (with episodes) by URL, URI, or ID.
No parameter schema on file.
Search across tracks, albums, artists, playlists, shows, and episodes.
No parameter schema on file.
List the built-in editorial charts (key, name, backing playlist id).
No parameter schema on file.
Fetch an editorial chart (e.g. 'top-50-global') as a playlist.
No parameter schema on file.
Fetch artists related to an artist ('fans also like').
No parameter schema on file.
Fetch an artist's full discography (albums, singles, compilations).
No parameter schema on file.
Recommend albums similar to a track.
No parameter schema on file.
Extract a cover image's theming colors (image URL/uri, or any entity URL/URI/ID).
No parameter schema on file.
Fetch an artist's upcoming concerts/events.
No parameter schema on file.
Fetch many tracks at once; one ordered result per input, failures captured per item.
No parameter schema on file.
Fetch many albums at once; one ordered result per input, failures captured per item.
No parameter schema on file.
Fetch many artists at once; one ordered result per input, failures captured per item.
No parameter schema on file.
Fetch many episodes at once; one ordered result per input, failures captured per item.
No parameter schema on file.
Fetch many playlists at once (up to ``max_tracks`` each); failures captured per item.
No parameter schema on file.
Fetch many shows at once (up to ``max_episodes`` each); failures captured per item.
No parameter schema on file.
Fetch a track's Canvas looping video (needs SPOTIFY_SP_DC).
No parameter schema on file.
Fetch a track's credits — performers, writers, producers (needs SPOTIFY_SP_DC).
No parameter schema on file.
Fetch a public user profile (needs SPOTIFY_SP_DC).
No parameter schema on file.
Fetch a track's lyrics (needs SPOTIFY_SP_DC).
No parameter schema on file.
Fetch a podcast episode's transcript (needs SPOTIFY_SP_DC).
No parameter schema on file.
Fetch the logged-in account's product state (needs SPOTIFY_SP_DC).
No parameter schema on file.
Return an entity's cover art as an inline image.
No parameter schema on file.
Fetch a track plus its cover ``colors`` and ``canvas`` in one call, for visual UIs.
No parameter schema on file.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Spotifyscraper costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | metadata | inspection depth (metadata) — how much of the target the scan could see | −8 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 3.9.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Writing one takes an account with at least 50 real tool calls against Spotifyscraper in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.