_ registry / mcp http-sse · checked 49m ago

bandmixr

https://bandmixr.com

Registry code: c3337e7fe45e93ea

api record

Bandmixr is an online mixing and mastering service for musicians. master_song opens the Bandmixr studio for a finished song: the song is checked in the browser and a 30-second mastered preview plays next to the original; the full master needs a Bandmixr account. check_mix opens the same studio focused on the report (loudness, true peak, clipping, stereo image, tonal balance). Songs dropped into the studio are analyzed in the browser, not uploaded, for the check. Mixing stems needs the person to connect their Bandmixr account: create_song (or open_song_studio for an existing song) opens the…

endpoint
https://bandmixr.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is bandmixr live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is bandmixr free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does bandmixr have?
15 tools: open_song_studio, master_song, list_songs, get_song_status, create_song, update_song, get_song_session, prepare_full_master, ….
Is bandmixr safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
506ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
2 open1 auth-required 12 never probed 3 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_mix open 49m ago

    Opens the Bandmixr Mix Analyzer in the chat. It checks a mix or master in the browser (the file is not uploaded): loudness (LUFS), true peak, clipping, stereo image and tonal balance, with a verdict for each and a 30-second mastered preview.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "genre": {
          "enum": [
            "rock_indie",
            "pop",
            "acoustic",
            "hip_hop_grime",
            "electronic",
            "reggae_dub",
            "orchestral",
            "metal",
            "jazz",
            "blues",
            "funk_soul",
            "punk",
            "other"
          ],
          "type": "string",
          "description": "Genre of the song. rock_indie = rock / indie; pop = pop; acoustic = acoustic, singer-songwriter; hip_hop_grime = hip hop, rap, trap, grime; electronic = electronic, EDM, house, techno; reggae_dub = reggae / dub; orchestral = orchestral, film score; metal = metal; jazz = jazz; blues = blues; funk_soul = funk / soul / R&B; punk = punk; other = anything else or not sure (balanced, genre-neutral)."
        }
      }
    }
    arguments 25 lines
  • get_analyzer_session open 49m ago

    Returns a 30-minute ticket and the address of the Bandmixr preview service, which the studio in the chat uses for the 30-second mastered preview. The studio calls this tool on its own; the assistant does not need to call it directly.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_account auth-required 49m ago

    Shows the connected Bandmixr account's plan and its limits (stems per song, song length, storage). Needs the person to connect their Bandmixr account.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • open_song_studio unknown never probed

    Opens the Bandmixr studio for a song in the chat. It shows what the song needs next: the upload box for stems, the label check (only the person can confirm labels there), the mix progress, or the player with the original, the mix and the master.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId"
      ],
      "properties": {
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 15 lines
  • master_song unknown never probed

    Opens the Bandmixr studio in the chat to master or enhance a finished song (a stereo mix). The song is checked in the browser for loudness, peaks, stereo image and tonal balance, and a 30-second mastered preview plays next to the original. Mastering the full song needs a Bandmixr account.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "genre": {
          "enum": [
            "rock_indie",
            "pop",
            "acoustic",
            "hip_hop_grime",
            "electronic",
            "reggae_dub",
            "orchestral",
            "metal",
            "jazz",
            "blues",
            "funk_soul",
            "punk",
            "other"
          ],
          "type": "string",
          "description": "Genre of the song. rock_indie = rock / indie; pop = pop; acoustic = acoustic, singer-songwriter; hip_hop_grime = hip hop, rap, trap, grime; electronic = electronic, EDM, house, techno; reggae_dub = reggae / dub; orchestral = orchestral, film score; metal = metal; jazz = jazz; blues = blues; funk_soul = funk / soul / R&B; punk = punk; other = anything else or not sure (balanced, genre-neutral)."
        },
        "preset": {
          "enum": [
            "streaming",
            "optimal",
            "loud"
          ],
          "type": "string",
          "description": "Mastering style. streaming = optimized for Spotify and Apple Music; optimal = balanced (\"Standard\"); loud = maximum punch and loudness."
        }
      }
    }
    arguments 34 lines
  • list_songs unknown never probed

    Lists the person's Bandmixr songs, most recently changed first.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_song_status unknown never probed

    One song's stems with their labels, uploads and analysis still running, whether the person has confirmed the labels, and where the mix and master stand.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId"
      ],
      "properties": {
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 15 lines
  • create_song unknown never probed

    Creates a new song in Bandmixr for mixing stems and opens the studio with its upload box. The genre and the mastering style are the ones the person names (other and streaming when they name none). Mixing and mastering are part of it: they start by themselves once the stems are uploaded and the person has confirmed the labels in the studio.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "mix": {
          "type": "boolean",
          "description": "false = upload now, mix later (default true: mix once the labels are confirmed)."
        },
        "genre": {
          "enum": [
            "rock_indie",
            "pop",
            "acoustic",
            "hip_hop_grime",
            "electronic",
            "reggae_dub",
            "orchestral",
            "metal",
            "jazz",
            "blues",
            "funk_soul",
            "punk",
            "other"
          ],
          "type": "string",
          "description": "Genre of the song. rock_indie = rock / indie; pop = pop; acoustic = acoustic, singer-songwriter; hip_hop_grime = hip hop, rap, trap, grime; electronic = electronic, EDM, house, techno; reggae_dub = reggae / dub; orchestral = orchestral, film score; metal = metal; jazz = jazz; blues = blues; funk_soul = funk / soul / R&B; punk = punk; other = anything else or not sure (balanced, genre-neutral)."
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "The song's name, as the person calls it."
        },
        "preset": {
          "enum": [
            "streaming",
            "optimal",
            "loud"
          ],
          "type": "string",
          "description": "Mastering style. streaming = optimized for Spotify and Apple Music; optimal = balanced (\"Standard\"); loud = maximum punch and loudness."
        }
      }
    }
    arguments 44 lines
  • update_song unknown never probed

    Changes the title or the genre of a song (not while it is being mixed).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId"
      ],
      "properties": {
        "genre": {
          "enum": [
            "rock_indie",
            "pop",
            "acoustic",
            "hip_hop_grime",
            "electronic",
            "reggae_dub",
            "orchestral",
            "metal",
            "jazz",
            "blues",
            "funk_soul",
            "punk",
            "other"
          ],
          "type": "string",
          "description": "Genre of the song. rock_indie = rock / indie; pop = pop; acoustic = acoustic, singer-songwriter; hip_hop_grime = hip hop, rap, trap, grime; electronic = electronic, EDM, house, techno; reggae_dub = reggae / dub; orchestral = orchestral, film score; metal = metal; jazz = jazz; blues = blues; funk_soul = funk / soul / R&B; punk = punk; other = anything else or not sure (balanced, genre-neutral)."
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "The song's name, as the person calls it."
        },
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 40 lines
  • get_song_session unknown never probed

    Returns a 15-minute ticket for one of the person's songs, which the studio in the chat uses to upload stems, show the label check and the progress, and play the original, the mix and the master. The studio calls this tool on its own; the assistant does not need to call it directly.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId"
      ],
      "properties": {
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 15 lines
  • prepare_full_master unknown never probed

    Creates a new song named after the file the person checked in the studio and returns a short-lived ticket for uploading it, so the studio can upload and master the full song. The studio calls this tool when the person chooses to master the full song; the assistant does not need to call it directly.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "title"
      ],
      "properties": {
        "genre": {
          "enum": [
            "rock_indie",
            "pop",
            "acoustic",
            "hip_hop_grime",
            "electronic",
            "reggae_dub",
            "orchestral",
            "metal",
            "jazz",
            "blues",
            "funk_soul",
            "punk",
            "other"
          ],
          "type": "string",
          "description": "Genre of the song. rock_indie = rock / indie; pop = pop; acoustic = acoustic, singer-songwriter; hip_hop_grime = hip hop, rap, trap, grime; electronic = electronic, EDM, house, techno; reggae_dub = reggae / dub; orchestral = orchestral, film score; metal = metal; jazz = jazz; blues = blues; funk_soul = funk / soul / R&B; punk = punk; other = anything else or not sure (balanced, genre-neutral)."
        },
        "title": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1
        }
      }
    }
    arguments 33 lines
  • set_stem_labels unknown never probed

    Sets what is on each stem from what the person says about their files (stem ids and file names come from get_song_status). It does not confirm the labels: the person still confirms them with "Labels are correct" in the studio before anything is mixed.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId",
        "labels"
      ],
      "properties": {
        "labels": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "stemId",
              "label"
            ],
            "properties": {
              "label": {
                "enum": [
                  "kick",
                  "snare",
                  "hihat",
                  "toms",
                  "overheads",
                  "room_mics",
                  "drum_bus",
                  "percussion",
                  "bass_electric",
                  "bass_acoustic",
                  "bass_synth",
                  "guitar_electric_clean",
                  "guitar_electric_distorted",
                  "guitar_acoustic",
                  "guitar_nylon",
                  "piano",
                  "organ",
                  "synth_pad",
                  "synth_lead",
                  "keys_other",
                  "vocal_lead",
                  "vocal_backing",
                  "vocal_rap",
                  "strings",
                  "brass",
                  "woodwinds",
                  "instrumental",
                  "ambient",
                  "other"
                ],
                "type": "string",
                "description": "What is on the stem. kick = kick drum; snare = snare drum; hihat = hi-hat; toms = toms; overheads = drum overheads (cymbals and the whole kit from above); room_mics = drum room mics; drum_bus = all drums on one track (drum mix or drum loop); percussion = percussion (shaker, congas, claps, tambourine); bass_electric = electric bass guitar; bass_acoustic = upright or acoustic bass; bass_synth = synth bass or 808; guitar_electric_clean = clean electric guitar; guitar_electric_distorted = distorted or overdriven electric guitar; guitar_acoustic = acoustic guitar (steel strings); guitar_nylon = nylon-string or classical guitar; piano = piano; organ = organ; synth_pad = synth pad; synth_lead = synth lead; keys_other = other keys (Rhodes, e-piano, keyboard); vocal_lead = lead vocal (the main sung vocal); vocal_backing = backing vocals, harmonies or ad-libs; vocal_rap = rap vocal; strings = strings (violin, cello, string section); brass = brass (trumpet, trombone, horns); woodwinds = woodwinds (flute, sax, clarinet); instrumental = full instrumental or beat (everything but the vocals on one stereo track); ambient = ambience, effects, textures or noise; other = something else, or not sure."
              },
              "stemId": {
                "type": "string",
                "maxLength": 64,
                "minLength": 1
              }
            }
          },
          "maxItems": 64,
          "minItems": 1
        },
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 70 lines
  • mix_and_master unknown never probed

    Mixes an existing song's stems and masters the mix in one go (draft, final mix, master), for example to mix it again with another genre or mastering style; a song made with create_song is already set up for this. It waits for the uploads, the analysis and the person's "Labels are correct" in the studio, then starts by itself. The mastering style is the one the person names (streaming when they name none). The studio shows the progress and plays the result; a new mix replaces the earlier version made in the chat (downloaded versions and mixes made on the website stay).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId"
      ],
      "properties": {
        "master": {
          "type": "boolean",
          "description": "false = mix only, without a master (default true)."
        },
        "preset": {
          "enum": [
            "streaming",
            "optimal",
            "loud"
          ],
          "type": "string",
          "description": "Mastering style. streaming = optimized for Spotify and Apple Music; optimal = balanced (\"Standard\"); loud = maximum punch and loudness."
        },
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 28 lines
  • start_mastering unknown never probed

    Masters the song's finished mix, or masters it again in another style (for example "louder": loud). The song needs a finished mix, from mix_and_master or an uploaded mix. The studio shows the progress and plays the new master, which replaces an earlier master made in the chat (downloaded ones stay).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId",
        "preset"
      ],
      "properties": {
        "preset": {
          "enum": [
            "streaming",
            "optimal",
            "loud"
          ],
          "type": "string",
          "description": "Mastering style. streaming = optimized for Spotify and Apple Music; optimal = balanced (\"Standard\"); loud = maximum punch and loudness."
        },
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        }
      }
    }
    arguments 25 lines
  • adjust_mix unknown never probed

    Changes a song mixed from stems the way the person asks after listening: a stem louder or quieter, muted or back in, more or less reverb, or placed left, center or right. One call takes all the changes for a song. Bandmixr then makes the mix and the master again with the changes (about as long as the first mix); the studio shows the progress and plays the new version, which replaces the earlier version made in the chat (downloaded versions and mixes made on the website stay). Stem ids, file names and the current settings come from get_song_status.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "songId",
        "changes"
      ],
      "properties": {
        "preset": {
          "enum": [
            "streaming",
            "optimal",
            "loud"
          ],
          "type": "string",
          "description": "Mastering style for the new master; the current one if not given."
        },
        "songId": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "The song id from list_songs or create_song."
        },
        "changes": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "stemId"
            ],
            "properties": {
              "pan": {
                "enum": [
                  "auto",
                  "left",
                  "center",
                  "right"
                ],
                "type": "string",
                "description": "Where the stem sits from left to right. auto = Bandmixr places it; left = to the left; center = in the center; right = to the right."
              },
              "muted": {
                "type": "boolean",
                "description": "true = leave the stem out of the mix; false = bring it back."
              },
              "reverb": {
                "enum": [
                  "default",
                  "none",
                  "low",
                  "medium",
                  "high"
                ],
                "type": "string",
                "description": "How much reverb the stem gets. default = Bandmixr's own amount; none = no reverb (dry); low = less reverb than Bandmixr's amount; medium = more reverb than Bandmixr's amount; high = a lot of reverb."
              },
              "stemId": {
                "type": "string",
                "maxLength": 64,
                "minLength": 1,
                "description": "The stem id from get_song_status."
              },
              "volumeDb": {
                "type": "number",
                "maximum": 12,
                "minimum": -24,
                "description": "The stem's new level against Bandmixr's own balance in dB: 0 = Bandmixr's balance, +3 = 3 dB louder, -6 = 6 dB quieter. It replaces the current value (get_song_status shows it), so \"a bit louder\" from +2 is +4. About 1 to 2 dB is \"a bit\", 3 to 4 dB \"clearly\", 6 dB \"a lot\"."
              }
            }
          },
          "maxItems": 64,
          "minItems": 1
        }
      }
    }
    arguments 75 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c3337e7fe45e93ea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c3337e7fe45e93ea/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c3337e7fe45e93ea/badge.svg)](https://brick.blue/agent/c3337e7fe45e93ea?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.