# Spotify (npm · @pipeworx/mcp-spotify)

Spotify MCP — Web API via client_credentials OAuth

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-spotify/spotify-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-spotify/spotify-mcp)
- npm · `@pipeworx/mcp-spotify`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify.md), [page](https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-spotify`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-spotify).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 432 tokens (~72/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Spotify MCP server?

Spotify runs locally as an npm package, launched with npx -y @pipeworx/mcp-spotify. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-spotify -- npx -y @pipeworx/mcp-spotify
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-spotify": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-spotify"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-spotify": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-spotify"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-spotify -- npx -y @pipeworx/mcp-spotify
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-spotify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-spotify"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-spotify --command npx --arg -y --arg @pipeworx/mcp-spotify
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-spotify:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-spotify"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-spotify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-spotify"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-spotify -t stdio -c npx -a -y @pipeworx/mcp-spotify
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-spotify": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-spotify"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 84, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (6)

### `search` (~117 tokens)

Search the Spotify catalog. type = comma-separated of album, artist, playlist, track, show, episode, audiobook. Returns matched items in named sections.

Input parameters:

- `limit` (number): 1-50 (default 20)
- `market` (string): ISO 3166-1 alpha-2 market code (e.g., "US")
- `offset` (number): 0-1000 (default 0)
- `query` (string, required): Search query
- `type` (string): Comma-separated types (default "track")

### `get_track` (~50 tokens)

Single track by Spotify ID. Returns artists, album, popularity, preview URL, duration.

Input parameters:

- `market` (string): Market for availability
- `track_id` (string, required): Spotify track ID (base62)

### `get_artist` (~32 tokens)

Artist record: name, genres, popularity, followers, images.

Input parameters:

- `artist_id` (string, required): Spotify artist ID

### `get_album` (~70 tokens)

Fetch a Spotify album by album_id. Returns name, artists, release date, total tracks, label, genres, popularity, images, and full tracklist with track IDs and durations. Optional market filter.

Input parameters:

- `album_id` (string, required): Spotify album ID
- `market` (string): Market for availability

### `get_artist_top_tracks` (~47 tokens)

Top tracks for an artist in a market (Spotify recommendation).

Input parameters:

- `artist_id` (string, required): Spotify artist ID
- `market` (string): ISO market code (default "US")

### `get_audio_features` (~65 tokens)

Audio features for a track: tempo (BPM), key, mode (major/minor), time_signature, energy, danceability, valence, acousticness, instrumentalness, liveness, speechiness, loudness.

Input parameters:

- `track_id` (string, required): Spotify track ID

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Spotify MCP server?

Spotify is an MCP server listed in the public MCP registry as io.github.pipeworx-io/spotify. Spotify MCP, Web API via client_credentials OAuth. This page covers its npm package (@pipeworx/mcp-spotify).

### Is the Spotify MCP server safe to use?

Spotify scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 MCP server expose?

Spotify exposes 6 tools: search, get_track, get_artist, get_album, get_artist_top_tracks, get_audio_features. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.

### Is the Spotify MCP server still maintained?

Spotify is still listed as active in the MCP registry. We last reached this channel on 5 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 MCP server under?

Spotify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-spotify
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-spotify
- Repository: https://github.com/pipeworx-io/mcp-spotify
- Website: https://pipeworx.io/packs/spotify
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-spotify/pipeworx-mcp-spotify