Remote MCP · Endpoint

Bandmixr MCP server

No. Bandmixr answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://bandmixr.com/mcp

The last check completed an MCP handshake.

Registry name
com.bandmixr/bandmixr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
320 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI mixing and mastering in the chat: check a song, mix your stems, change the mix in plain words.
Listing
From the official MCP registry (active).
Recent checks of Bandmixr
CheckedResultHandshake
13 minutes agoHandshake completed320 ms
10 days agoHandshake completed305 ms
10 days agoHandshake completed310 ms
11 days agoHandshake completed304 ms
13 days agoHandshake completed330 ms
14 days agoHandshake completed310 ms
14 days agoHandshake completed303 ms
15 days agoHandshake completed515 ms
17 days agoHandshake completed313 ms
19 days agoHandshake completed306 ms
21 days agoHandshake completed304 ms
24 days agoHandshake completed312 ms
26 days agoHandshake completed306 ms
28 days agoHandshake completed1.03 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Bandmixr and makes no claim about it beyond what these checks measured.