io.github.jamiew/spotify-mcp

Name: io.github.jamiew/spotify-mcp
Rating: 60 (1 reviews)
Author: io.github.jamiew

MCPcommunity

v0.3.1io.github.jamiewUnknownUpdated 1mo agoGitHub

MCP server connecting LLMs to Spotify, with smart-batching and large-playlist tools

mcp-name: io.github.jamiew/spotify-mcp MCP server connecting Claude with Spotify. This fork of varunneal/spotify-mcp adds smart-batching tools and advanced playlist features that optimize API usage. Playback Control: Start, pause, skip tracks, manage queue Search & Discovery: Find tracks, albums, artists, playlists with pagination Real-time State: Live user profile and playback status Resources:…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.jamiew

LicenseUnknown

Version0.3.1

Sourcemcp-registry

GitHubjamiew/spotify-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ Cleanv0.3.1 · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp