SpotifyScraper

Extract public Spotify data, tracks, albums, artists, playlists, podcasts & lyrics, without the official API. Sync + async, typed models, one dependency.

Runssource: GitHubhomepagePythonMITcommit 9cbf05aa4963

Python, MIT licensed. The project labels itself: async, claude, httpx, llm, lyrics, mcp, mcp server and metadata.

SpotifyScraper runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The SpotifyScraper package is installed and working: the CLI fetches real Spotify track/artist/playlist data over the network, the hermetic unit test suite passes completely (921/921), and the MCP server imports and launches correctly after pinning mcp to v1.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
325
forks
33
open issues
15
watchers
14
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing SpotifyScraper, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • mcp 2.3.0 installed by default is incompatible with the project's FastMCP import (mcp<2 required by pyproject.toml but pin was ignored by pip dependency resolution)1 minute
Install time
2 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
spotifyscraper track 4uLU6hMCjMI75M1A2tKUQC returned valid JSON with name='Never Gonna Give You Up'; artist, playlist, search live calls all returned real Spotify data; pytest ran 921 passed 0 failed
Model tokens used
246,704
Exact commit tested
9cbf05aa4963
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

\" 2>&1" in /work/repo
 succeeded in 2151ms:
Artist: Rick Astley | Followers: 1626390
Playlist: Today’s Top Hits | Tracks: 50
Search total: 18
Live API verification complete
All verified end-to-end. Here is my final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "er…
tokens used
246,704
All verified end-to-end. Here is my final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "er…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes, faster than the median of the 7 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 8 async projects Argusic has installed and timed, SpotifyScraper was the 2nd fastest to reach a running state, and 7 of 8 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

asyncclaudehttpxllmlyricsmcpmcp-servermetadatamodel-context-protocolmusicno-api-keypodcastpythonscraperspotifyspotify-apispotify-lyricsspotify-scraperspotify-web-playerweb-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/SpotifyScraper.svg)](https://argusic.com/subject/spotifyscraper)

Questions

Does SpotifyScraper run?
Yes. SpotifyScraper runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test SpotifyScraper?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9cbf05aa4963. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test SpotifyScraper?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does SpotifyScraper take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does SpotifyScraper need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing SpotifyScraper?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does SpotifyScraper compare with the alternatives?
Of the 8 async projects Argusic has installed and timed, SpotifyScraper was the 2nd fastest to reach a running state, and 7 of 8 reached one at all.
Where is the evidence for SpotifyScraper?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion