spotify-library-mcp (oliver-virt/spotify-library-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

spotify-library-mcp

Enables you to manage your personal Spotify library from Claude or a CLI, including organizing playlists, merging and deleting playlists, saving tracks, searching with artist verification, and querying top tracks, artists, and recently played items.

→ oliver-virt/spotify-library-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

oliver-virt

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: MCP_SECRET, SPOTIFY_CLIENT_SECRET, SPOTIFY_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHOST
🔐 secretMCP_SECRET
configSPOTIFY_ACCOUNTS_URL
configSPOTIFY_API_URL
configSPOTIFY_BUDGET_FILE
🔐 secretSPOTIFY_CLIENT_SECRET
configSPOTIFY_INDEX_TTL_MS
configSPOTIFY_MIN_GAP_MS
🔐 secretSPOTIFY_REFRESH_TOKEN
configSPOTIFY_SEARCH_DAILY_CAPpersistent daily budget (default 800, SPOTIFY_SEARCH_DAILY_CAP), result cache, ban memory — see below
configSPOTIFY_SNAPSHOT_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/oliver-virt/spotify-library-mcp)](https://m8ven.ai/mcp/oliver-virt/spotify-library-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bd99eb2bba0ff76569cb96b659cab562378c908a
code hash: 07c0bce649199cfcca1ebdf6ec71a97d00a6f9d9ec0c62a1c5ae92c529f94ab2
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client