Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Deezer

NPM · @PIPEWORX/MCP-DEEZER · 2 COMPONENTS

Deezer MCP — public catalog (no auth required).

+3 this week 82 Trust /100

Last scanned (11 hours ago)

Scores higher than 72% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

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

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • 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. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-deezer@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-deezer
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-deezer/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3617495992
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:650e72347b69fe412228ee3e93d1154b68f46f19831095bb14acf8bec86b62fb749ee583ec975e7b26fa977f35c3897a81e924792cc9259146336e8d9

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~263 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
album ~25

Album metadata + tracklist by Deezer album id.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

artist ~22

Artist metadata by Deezer artist id.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

artist_top ~88

Deezer music catalogue — the most-streamed tracks for one Deezer artist id, up to 100. Each track returns its Deezer track id, title, rank, duration, album and a 30-second preview URL. Answers what an artist's biggest songs are on Deezer.

NameTypeReqDescription
idnumberyes–
limitnumber–1-100 (default 25)

No output schema declared.

No examples provided.

chart ~39

Current chart (top tracks/albums/artists). Pass genre_id 0 for worldwide.

NameTypeReqDescription
genre_idnumber–Default 0 (all genres).

No output schema declared.

No examples provided.

search ~67

Search Deezer for tracks/albums/artists/playlists.

NameTypeReqDescription
limitnumber–1-100 (default 25)
querystringyese.g. "Daft Punk Get Lucky"
typestring–track | album | artist | playlist (default track)

No output schema declared.

No examples provided.

track ~22

Track metadata by Deezer track id.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

Install

How do I install the Deezer MCP server?

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

npm · @pipeworx/mcp-deezer

# add to Claude Code
claude mcp add pipeworx-io-deezer -- npx -y @pipeworx/mcp-deezer
Common questions

What is the Deezer MCP server?

Deezer is an MCP server listed in the public MCP registry as io.github.pipeworx-io/deezer. Deezer MCP, public catalog (no auth required). This page covers its npm package (@pipeworx/mcp-deezer).

Is the Deezer MCP server safe to use?

Deezer scores 82 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 Deezer MCP server expose?

Deezer exposes 6 tools: search, track, album, artist, artist_top, chart. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.

Is the Deezer MCP server still maintained?

Deezer 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 Deezer MCP server under?

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