Skip to content

Bitsound MCP server

com.bitsound/bitsoundbitsound.comstreamable-httpv1.1.0Scanned

Search the Bitsound music store, manage collection and playlists, edit your releases as an artist.

38 tools: 5 can delete or cancel things, 3 do something that can't be undone, 16 change things and 14 only read.

Tools: 5 delete, 3 irreversible, 16 write, 14 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 1
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here can delete or cancel things and 3 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Bitsound MCP server can do

The Bitsound MCP server is published by bitsound.com, a domain the MCP Registry verified. It has 38 tools. It can delete or cancel things (5 tools: playlist_remove_tracks, playlist_delete, cart_remove, studio_free_access_revoke and 1 more), do things that cannot be undone, such as sending, paying or publishing (purchase_prepare, withdrawal_prepare and studio_comment_reply) and create or change data (16 tools: credits_balance, playlist_create, playlist_update, playlist_add_tracks and 12 more). 14 tools only read.

1 tool reads private data (studio_free_access_list); 1 tool can send data out of your system (studio_comment_reply).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

38 tools

Deletes or cancels 5Claude Code: deny
  • cart_removeRemove releases or tracks from the person's cart, or empty it with all.No findings

    Why it is in this group

    • The name "cart_remove" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Remove releases or tracks from the person's cart, or empty it with all.

    Annotations the server declares

    • title: Remove from my cart
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • playlist_deleteDelete one of the person's playlists.No findings

    Why it is in this group

    • The name "playlist_delete" says "delete": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete one of the person's playlists. This cannot be undone, ask the person first.

    Annotations the server declares

    • title: Delete a playlist
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • playlist_remove_tracksRemove tracks from one of the person's playlists.No findings

    Why it is in this group

    • The name "playlist_remove_tracks" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Remove tracks from one of the person's playlists.

    Annotations the server declares

    • title: Remove tracks from a playlist
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • studio_code_revokeRevoke a download code the person created, as long as it was not redeemed yet.No findings

    Why it is in this group

    • The name "studio_code_revoke" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke a download code the person created, as long as it was not redeemed yet. It can no longer be redeemed.

    Annotations the server declares

    • title: Revoke a download code
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • studio_free_access_revokeRevoke a free access link the person created, as long as it was not redeemed yet.No findings

    Why it is in this group

    • The name "studio_free_access_revoke" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke a free access link the person created, as long as it was not redeemed yet. The link stops working.

    Annotations the server declares

    • title: Revoke free access link
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 3Claude Code: ask
  • purchase_prepareNever buys anything and never spends money.No findings

    Why it is in this group

    • The name "purchase_prepare" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Never buys anything and never spends money. Checks prices for releases or tracks and returns links where the person confirms the purchase in the browser. With addToCart the items are put into the person's Bitsound cart, which the person checks out on the website.

    Annotations the server declares

    • title: Prepare a purchase for the person to confirm
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_comment_replyReply as the artist to a listener comment on one of the person's releases.Can send data outNo findings

    Why it is in this group

    • The name "studio_comment_reply" says "comment": a word for a change.
    • The name "studio_comment_reply" also says "reply": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "studio_comment_reply" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Reply as the artist to a listener comment on one of the person's releases. The reply is public under the person's artist name, so it is only saved as a draft: the person reads and confirms it in the browser (you get a confirmUrl to give them). Never put private links (download links, free access links, codes) into a reply.

    Annotations the server declares

    • title: Answer a comment
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • withdrawal_prepareNever withdraws anything by itself.1 finding

    Why it is in this group

    • The name "withdrawal_prepare" says "withdrawal": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "withdrawal_prepare" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "withdrawal_prepare" says "withdrawal": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Never withdraws anything by itself. Lists the person's recent purchases, top-ups, gift cards and storage plans and returns a link to the form "Withdraw from contract" on bitsound.com/withdrawal with the contract already chosen. The person checks the statement and sends it with "Confirm withdrawal" in the browser. Music purchases where the person agreed to the immediate download are usually no longer withdrawable; Bitsound checks every withdrawal.

    Annotations the server declares

    • title: Prepare a withdrawal from a contract for the person to confirm
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 16Claude Code: ask
  • credits_balanceThe person's Bitsound credit balance in EUR, split into paid credits and free promo vouchers from Bitsound (with scope and expiry).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The person's Bitsound credit balance in EUR, split into paid credits and free promo vouchers from Bitsound (with scope and expiry). Promo credit is spent first, does not pay out and expires on its date. Credits are topped up and spent only on the website.

    Annotations the server declares

    • title: My credit balance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • playlist_add_tracksAppend published tracks to one of the person's playlists in the given order, in one step.No findings

    Why it is in this group

    • The name "playlist_add_tracks" says "add": a word for a change.
    Description, as the server wrote it
    Append published tracks to one of the person's playlists in the given order, in one step. Tracks already in it are skipped, unknown or unpublished ones are counted as unavailable.

    Annotations the server declares

    • title: Add tracks to a playlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • playlist_createCreate a new playlist for the person, optionally with tracks (track IDs from get_release).No findings

    Why it is in this group

    • The name "playlist_create" says "create": a word for a change.
    Description, as the server wrote it
    Create a new playlist for the person, optionally with tracks (track IDs from get_release).

    Annotations the server declares

    • title: Create a playlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • playlist_updateChange title, description or visibility of one of the person's playlists.No findings

    Why it is in this group

    • The name "playlist_update" says "update": a word for a change.
    Description, as the server wrote it
    Change title, description or visibility of one of the person's playlists.

    Annotations the server declares

    • title: Rename or change a playlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • redeem_codeRedeem a Bitsound code for the signed-in person: a download code from an artist (BSND-XXXX-XXXX, puts a release or track into the collection) or a gift code (GIFT-XXXX-XXXX-XXXX: m…No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Redeem a Bitsound code for the signed-in person: a download code from an artist (BSND-XXXX-XXXX, puts a release or track into the collection) or a gift code (GIFT-XXXX-XXXX-XXXX: music given as a gift, a free promo voucher from Bitsound, or a gift card bought earlier). A redeem link (https://bitsound.com/redeem?code=...) works too. Every code works once. Rate limited.

    Annotations the server declares

    • title: Redeem a code
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_artist_updateChange name, bio, location or links of one of the person's artist projects.No findings

    Why it is in this group

    • The name "studio_artist_update" says "update": a word for a change.
    Description, as the server wrote it
    Change name, bio, location or links of one of the person's artist projects. The profile is public, so the change waits until the person confirms it in the browser (you get a confirmUrl to give them). Links replace the whole list. Only the given fields change.

    Annotations the server declares

    • title: Edit my artist profile
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_codes_createCreate free download codes for one of the person's releases (published or scheduled), e.g.No findings

    Why it is in this group

    • The name "studio_codes_create" says "create": a word for a change.
    Description, as the server wrote it
    Create free download codes for one of the person's releases (published or scheduled), e.g. for cards at a concert or for the press. Each code unlocks the whole release or one track once, forever, in all formats, like a purchase at 0 EUR (no money, no fee, counts as given away). Returns the codes with their redeem links. Optional label only the artist sees and an expiry date. Limit per release. The codes are only created after the person confirms count and release in the browser (you get a confirmUrl to give them), afterwards studio_request_status returns them.

    Annotations the server declares

    • title: Create download codes
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_commentsNewest comments from listeners on the person's releases, with replies.1 finding

    Why it is in this group

    • The name "studio_comments" says "comment": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "studio_comments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "studio_comments" says "comment": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Newest comments from listeners on the person's releases, with replies. Names only as the commenters show them publicly.

    Annotations the server declares

    • title: Comments on my releases
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_free_access_createCreate a free access link for releases of one of the person's artist projects and return it.No findings

    Why it is in this group

    • The name "studio_free_access_create" says "create": a word for a change.
    Description, as the server wrote it
    Create a free access link for releases of one of the person's artist projects and return it. Bitsound sends no email: the person passes the link on themselves. Whoever opens it first and signs in or creates an account gets the releases in their collection like a purchase at 0 EUR (all download formats, no money, no fee); after that the link is used up. Either chosen releases (published or scheduled) or allMusic for every release published right now. Optional short note only the artist sees, e.g. who the link is for. Limits: per artist and day, and a maximum of open links. The link is only created after the person confirms it in the browser (you get a confirmUrl to give them), afterwards studio_request_status returns it. The link is private: never put it into public texts.

    Annotations the server declares

    • title: Create a free access link
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_overviewThe artist projects of the signed-in person with all their releases in every status (draft, in review, scheduled, published, rejected), plus the collecting society status.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The artist projects of the signed-in person with all their releases in every status (draft, in review, scheduled, published, rejected), plus the collecting society status. Bitsound only sells music without collecting societies: if the person reported a membership (collectingSociety.member true), none of their releases can be bought.

    Annotations the server declares

    • title: My artist projects and releases
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_release_updateChange details of one of the person's releases.No findings

    Why it is in this group

    • The name "studio_release_update" says "update": a word for a change.
    Description, as the server wrote it
    Change details of one of the person's releases. Drafts can change everything and change at once; after publishing only description and price can change, and because that is public the change waits until the person confirms it in the browser (you get a confirmUrl to give them). Releases in review or scheduled are locked. Only the given fields change.

    Annotations the server declares

    • title: Edit one of my releases
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • studio_request_statusShows whether the person confirmed or rejected what you asked for (comment replies, changes to published releases or the artist profile, download codes, free access links).1 finding

    Why it is in this group

    • The name "studio_request_status" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "studio_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "studio_request_status" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Shows whether the person confirmed or rejected what you asked for (comment replies, changes to published releases or the artist profile, download codes, free access links). With request: that one request with its result, e.g. the created codes or link. Without: the latest requests. Status pending, done, failed, rejected or expired (after 7 days).

    Annotations the server declares

    • title: Status of my confirmation requests
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_statsPlays, full listens, completion, likes, comments and sales for one of the person's artist projects (per release) or one release (per track).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Plays, full listens, completion, likes, comments and sales for one of the person's artist projects (per release) or one release (per track).

    Annotations the server declares

    • title: Statistics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_track_updateChange title, price, ISRC, lyrics, story or credits of one of the person's tracks.No findings

    Why it is in this group

    • The name "studio_track_update" says "update": a word for a change.
    Description, as the server wrote it
    Change title, price, ISRC, lyrics, story or credits of one of the person's tracks. After publishing title, price, lyrics, story and credits can still change, the ISRC not, and the change waits until the person confirms it in the browser (you get a confirmUrl to give them). Credits replace the whole list. Only the given fields change.

    Annotations the server declares

    • title: Edit one of my tracks
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • wishlist_setPut a published release on the person's wishlist or take it off.No findings

    Why it is in this group

    • The name "wishlist_set" says "set": a word for a change.
    Description, as the server wrote it
    Put a published release on the person's wishlist or take it off.

    Annotations the server declares

    • title: Add to or remove from the wishlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 14Show 14 read-only tools
  • cart_listThe person's Bitsound cart: titles, prices, total, credit balance and the amount missing.No findings

    Why it is in this group

    • The name "cart_list" says "list": a word for reading.
    Description, as the server wrote it
    The person's Bitsound cart: titles, prices, total, credit balance and the amount missing.

    Annotations the server declares

    • title: My cart
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_artistAn artist on Bitsound: bio, location, links and all published releases.No findings

    Why it is in this group

    • The name "get_artist" says "get": a word for reading.
    Description, as the server wrote it
    An artist on Bitsound: bio, location, links and all published releases.

    Annotations the server declares

    • title: Artist details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_releaseDetails of one published release: title, artist, genre and second genre, description, price, AI label, audio quality and the track list with track IDs, durations, prices and moods.No findings

    Why it is in this group

    • The name "get_release" says "get": a word for reading.
    Description, as the server wrote it
    Details of one published release: title, artist, genre and second genre, description, price, AI label, audio quality and the track list with track IDs, durations, prices and moods.

    Annotations the server declares

    • title: Release details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_trackOne published track with lyrics, the story behind the song, credits, moods, duration, price and its release.No findings

    Why it is in this group

    • The name "get_track" says "get": a word for reading.
    Description, as the server wrote it
    One published track with lyrics, the story behind the song, credits, moods, duration, price and its release.

    Annotations the server declares

    • title: Track details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • library_listReleases and tracks the signed-in person has bought, newest purchase first.No findings

    Why it is in this group

    • The name "library_list" says "list": a word for reading.
    Description, as the server wrote it
    Releases and tracks the signed-in person has bought, newest purchase first. Optional text filter on title or artist.

    Annotations the server declares

    • title: My collection
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_new_releasesThe newest published releases on Bitsound, newest first, optionally only one genre.No findings

    Why it is in this group

    • The name "list_new_releases" says "list": a word for reading.
    Description, as the server wrote it
    The newest published releases on Bitsound, newest first, optionally only one genre.

    Annotations the server declares

    • title: New releases on Bitsound
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • playlist_getOne of the person's own playlists with its tracks in order.No findings

    Why it is in this group

    • The name "playlist_get" says "get": a word for reading.
    Description, as the server wrote it
    One of the person's own playlists with its tracks in order. ownEntries are the person's own files added in the Bitsound app (title, artist, album and duration only, they cannot be played or edited here).

    Annotations the server declares

    • title: Playlist with tracks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • playlists_listThe playlists of the signed-in person.No findings

    Why it is in this group

    • The name "playlists_list" says "list": a word for reading.
    Description, as the server wrote it
    The playlists of the signed-in person.

    Annotations the server declares

    • title: My playlists
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_codes_listDownload codes (BSND-XXXX-XXXX) of one of the person's artist projects across all releases, grouped by creation: release, track (or the whole release), label, created, expiry, how …No findings

    Why it is in this group

    • The name "studio_codes_list" says "list": a word for reading.
    Description, as the server wrote it
    Download codes (BSND-XXXX-XXXX) of one of the person's artist projects across all releases, grouped by creation: release, track (or the whole release), label, created, expiry, how many were created and redeemed, and every code with its redeem link and status (open, redeemed, expired, revoked). Also the releases codes can be created for and the limit per release.

    Annotations the server declares

    • title: Download codes I created
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_free_access_listFree access links created from one of the person's artist projects: own note, releases, date, status (open, redeemed, revoked) and the link while it is open, plus the releases that…Reads private dataNo findings

    Why it is in this group

    • The name "studio_free_access_list" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    Free access links created from one of the person's artist projects: own note, releases, date, status (open, redeemed, revoked) and the link while it is open, plus the releases that can be given, today's count against the daily limit and the number of open links against their limit.

    Annotations the server declares

    • title: Free access links I created
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_release_getAll details of one of the person's own releases in any status, with tracks, metadata and which fields can still be edited.No findings

    Why it is in this group

    • The name "studio_release_get" says "get": a word for reading.
    Description, as the server wrote it
    All details of one of the person's own releases in any status, with tracks, metadata and which fields can still be edited.

    Annotations the server declares

    • title: One of my releases
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • studio_track_getOne of the person's own tracks with lyrics, story, credits, ISRC and price.No findings

    Why it is in this group

    • The name "studio_track_get" says "get": a word for reading.
    Description, as the server wrote it
    One of the person's own tracks with lyrics, story, credits, ISRC and price.

    Annotations the server declares

    • title: One of my tracks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • wishlist_listReleases on the person's wishlist with prices and the total.No findings

    Why it is in this group

    • The name "wishlist_list" says "list": a word for reading.
    Description, as the server wrote it
    Releases on the person's wishlist with prices and the total.

    Annotations the server declares

    • title: My wishlist
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
24
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://bitsound.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://bitsound.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 24 tools that change things (5 destructive, 3 irreversible, 16 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bitsound.com/mcp: tools/list returned 38 tools to an anonymous client, including playlist_remove_tracks (destructive), playlist_delete (destructive), cart_remove (destructive), studio_free_access_revoke (destructive), studio_code_revoke (destructive) and 19 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 24
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://bitsound.com/.well-known/oauth-protected-resource/mcp to none

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "withdrawal_prepare" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "withdrawal_prepare" says "withdrawal": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "studio_comments" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "studio_comments" says "comment": a word for a change.

    What this check looks for
  • The server marks "studio_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "studio_request_status" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 24 (and 3 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 24
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://bitsound.com/.well-known/oauth-protected-resource/mcp to none

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bitsound https://bitsound.com/mcp
claude mcp add --transport http bitsound https://bitsound.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bitsound__catalog_search",
      "mcp__bitsound__get_release",
      "mcp__bitsound__get_track",
      "mcp__bitsound__get_artist",
      "mcp__bitsound__list_new_releases",
      "mcp__bitsound__library_list",
      "mcp__bitsound__playlists_list",
      "mcp__bitsound__playlist_get",
      "mcp__bitsound__wishlist_list",
      "mcp__bitsound__cart_list",
      "mcp__bitsound__studio_release_get",
      "mcp__bitsound__studio_track_get",
      "mcp__bitsound__studio_free_access_list",
      "mcp__bitsound__studio_codes_list"
    ],
    "ask": [
      "mcp__bitsound__credits_balance",
      "mcp__bitsound__playlist_create",
      "mcp__bitsound__playlist_update",
      "mcp__bitsound__playlist_add_tracks",
      "mcp__bitsound__wishlist_set",
      "mcp__bitsound__download_link",
      "mcp__bitsound__purchase_prepare",
      "mcp__bitsound__redeem_code",
      "mcp__bitsound__withdrawal_prepare",
      "mcp__bitsound__studio_overview",
      "mcp__bitsound__studio_stats",
      "mcp__bitsound__studio_comments",
      "mcp__bitsound__studio_release_update",
      "mcp__bitsound__studio_track_update",
      "mcp__bitsound__studio_artist_update",
      "mcp__bitsound__studio_comment_reply",
      "mcp__bitsound__studio_free_access_create",
      "mcp__bitsound__studio_codes_create",
      "mcp__bitsound__studio_request_status"
    ],
    "deny": [
      "mcp__bitsound__playlist_remove_tracks",
      "mcp__bitsound__playlist_delete",
      "mcp__bitsound__cart_remove",
      "mcp__bitsound__studio_free_access_revoke",
      "mcp__bitsound__studio_code_revoke"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bitsound. Review it before you use it.

Capability tags behind 2 rules
  • mcp__bitsound__studio_comment_reply outbound
  • mcp__bitsound__studio_free_access_list private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bitsound/bitsound/verify?hash=ab20ff547033353bacc331d709648cff68edc3dc93a6a9f0b85fafa0417b9f0e" | jq -e '.changed == false'

Pinned hash ab20ff547033, from Nov 17, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bitsound/bitsound/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bitsound/bitsound
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bitsound/bitsound.svg)](https://radar.anlyon.com/servers/com.bitsound/bitsound)

Source: MCP Registry. Synced Nov 17, 2026, 14:17 UTC.

Bitsound MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Bitsound MCP server safe?

No scan can promise that. What its definitions show: 38 tools, 24 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Bitsound MCP server delete data?

Yes. 5 tools can delete, cancel or revoke something: playlist_remove_tracks, playlist_delete, cart_remove, studio_free_access_revoke and studio_code_revoke.

Can the Bitsound MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: purchase_prepare, withdrawal_prepare and studio_comment_reply.

What tools does the Bitsound MCP server have?

38 tools: 5 destructive, 3 irreversible, 16 write, 14 read. playlist_remove_tracks, playlist_delete, cart_remove, studio_free_access_revoke, studio_code_revoke, purchase_prepare, withdrawal_prepare, studio_comment_reply and 30 more.

Does the Bitsound MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Bitsound MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): studio_comment_reply.

Has the Bitsound MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.