Pipeworx musicbrainz

MusicBrainz MCP — wraps MusicBrainz Web Service v2 (free, no auth)

Security Scan

The skill's stated purpose (a MusicBrainz wrapper) is plausible, but the runtime instructions implicitly run a remote npm package via npx and route queries through a Pipeworx gateway — behavior that is not declared in the metadata and carries moderate risk.

Purpose & Capability

Name and description match a MusicBrainz wrapper. However, the SKILL.md's connect snippet requires running 'npx mcp-remote@latest' and contacting https://gateway.pipeworx.io/musicbrainz/mcp; the declared requirements list no required binaries (it should at minimum declare 'npx'). Using a third-party gateway rather than calling musicbrainz.org directly is a design choice but should be explicit.

Instruction Scope

The SKILL.md itself contains only a connect snippet and does not ask the agent to read local files or credentials. But it instructs the agent to execute an npm package (via npx) and to connect to a third-party endpoint (gateway.pipeworx.io), which means queries and possibly proxied data will flow to that service. This is within the apparent feature scope but increases data-exposure surface.

Install Mechanism

Although the skill has no declared install spec, the connect command uses 'npx -y mcp-remote@latest' which dynamically fetches and executes code from the npm registry at runtime. Fetching and running an unpinned 'latest' package is higher risk (lack of reproducibility, potential supply-chain issues). This implicit install/execution should have been declared and safer alternatives (pinned version, vetting instructions, or direct API calls) considered.

Credentials

The skill declares no environment variables, and the instructions don't request secrets or other credentials. There is no disproportionate credential request.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent privileges in its metadata. It does not modify other skills' configurations according to the provided data.

What to consider before installing

Before installing or invoking this skill, consider: 1) The SKILL.md expects 'npx' to run and will execute mcp-remote@latest — running an unpinned npm package at runtime can execute arbitrary code. If you need stronger assurance, ask for a pinned package version or inspect the mcp-remote source first. 2) Requests are proxied through gateway.pipeworx.io rather than calling MusicBrainz directly — review Pipeworx's privacy policy and trustworthiness because your queries (and potentially returned data) will pass through their gateway. 3) If you prefer minimal exposure, use a skill that calls musicbrainz.org directly or provide your own vetted proxy. 4) If you decide to use this skill, ensure 'npx' is available in a controlled runtime and consider running it in an environment with limited privileges.

MusicBrainz MCP — wraps MusicBrainz Web Service v2 (free, no auth). Free, no API key. Part of Pipeworx.

Tools

• search_artists
• get_artist
• search_releases
• get_release

Connect

{
  "mcpServers": {
    "pipeworx-musicbrainz": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/musicbrainz/mcp"]
    }
  }
}

More at pipeworx.io/packs/musicbrainz