Remote MCP · Endpoint

Music Studio MCP server

No. Music Studio answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://music-studio.linxule.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.linxule/mcp-music-studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
587 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
ABC sheet music + Strudel live coding: songs, videos and live jam sessions in ext-apps widgets.
Listing
From the official MCP registry (active).
Recent checks of Music Studio
CheckedResultHandshake
1 hour agoHandshake completed587 ms
2 days agoHandshake completed527 ms
4 days agoHandshake completed128 ms
6 days agoHandshake completed939 ms
8 days agoHandshake completed39 ms
9 days agoHandshake completed97 ms
11 days agoHandshake completed447 ms
12 days agoHandshake completed882 ms
13 days agoHandshake completed553 ms
16 days agoHandshake completed625 ms
17 days agoHandshake completed55 ms
19 days agoHandshake completed762 ms
20 days agoHandshake completed1.10 s
22 days agoHandshake completed365 ms
23 days agoHandshake completed474 ms

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

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 Music Studio and makes no claim about it beyond what these checks measured.