io.github.chrischall/musicbrainz-mcp

It requires MUSICBRAINZ_OAUTH_CLIENT_ID, MUSICBRAINZ_OAUTH_CLIENT_SECRET, MUSICBRAINZ_OAUTH_REFRESH_TOKEN, and a USER_AGENT. The OAuth client secret and refresh token are sensitive credentials; if exposed, they could be abused to perform user actions such as submitting tags, ratings, or collections. Based on the materials, these credentials appear related to the stated functionality, with no clear overreach red flag.

The description indicates it searches/browses MusicBrainz metadata and cover art, and submits tags/ratings/collections, so communication with MusicBrainz-related services is expected. The materials do not list specific hosts, which limits transparency about egress scope, but there is no explicit evidence of data being sent to unknown or unrelated endpoints.

The system checks indicate that the tool executes code / runs as a local MCP process. This is a normal MCP capability; the current materials do not show requests for unusual system privileges, unrelated command execution, or high-risk persistence behavior.

From the materials, it will at least access credential-bearing environment variables and handle data related to music metadata queries and user submissions. The missing README leaves local file access or cache locations unspecified, so the data-access boundary is not fully clear; however, the available information does not show excessive access beyond the stated function.

The source is an official registry entry, it is open source, and it has been updated within the last year, which are good auditability and maintenance signals. Low star count and an undeclared license slightly reduce confidence, but they do not amount to a high-risk supply-chain red flag.