Remote MCP · Endpoint

StemConsole MCP server

No. StemConsole answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://stemconsole.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.stemconsole/stemconsole
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Split songs into vocals, drums, bass, guitar and piano stems, in batches; manage songs and setlists
Listing
From the official MCP registry (active).
Recent checks of StemConsole
CheckedResultHandshake
6 hours agoHandshake completed93 ms
9 days agoHandshake completed100 ms
10 days agoHandshake completed123 ms
11 days agoHandshake completed294 ms
12 days agoHandshake completed106 ms
14 days agoHandshake completed179 ms
15 days agoHandshake completed134 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed110 ms
19 days agoHandshake completed74 ms
22 days agoHandshake completed199 ms
24 days agoHandshake completed84 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed241 ms

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

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