Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StemConsole

REMOTE · STEMCONSOLE.AI · 2 COMPONENTS

Split songs into vocals, drums, bass, guitar and piano stems, in batches; manage songs and setlists

65 Trust /100

Last scanned (20 hours ago)

Scores higher than 48% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1093 tokens (~84/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1
    • Tool “rename_song” is now declared destructive security
    • Stability: unverified → 0.03 ▲ functional
  • 18 Oct 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://stemconsole.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stemconsole.ai CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 af6ab09980e69ef61364f2efe65a53fa
SANs: stemconsole.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of stemconsole.ai. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
stemconsole.ai. present 2371 13 Verified
stemconsole.ai. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stemconsole.ai/mcp Verified 200
http (plaintext) http://stemconsole.ai/mcp HTTPS enforced 301 https://stemconsole.ai/mcp
MCP tools · 13 exposed · ~947 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_setlist ~78

Make a setlist from the connected account's songs: one share link that opens them in order in the browser, for a band or a class. Anyone can open the link. Free accounts make setlists of up to 3 songs, Pro up to 50.

NameTypeReqDescription
split_idsarrayyes–
titlestringyes–

No output schema declared.

No examples provided.

delete_song ~60

Permanently delete one of the connected account's songs and its stems. Its share link stops working. This cannot be undone, so confirm with the user first.

NameTypeReqDescription
split_idstringyesA split id from split_songs or list_my_songs.

No output schema declared.

No examples provided.

get_batch ~44

Progress of a batch from split_songs: each song's status (queued, starting, processing, done, failed) and split id.

NameTypeReqDescription
batch_idstringyes–

No output schema declared.

No examples provided.

get_capabilities ~44

Describe what StemConsole can do, the available stems, and pricing: Free, Pro (monthly or yearly), any current free trial and single-song credits. No input required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_account ~51

The connected account's plan (free or pro), splits used and left this month, credits, and the API limits (songs per hour, splits at once, batch size). Needs a connected StemConsole account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_split ~81

Status of one split and, once done, each stem's MP3 and preview links (plus WAV links and a ZIP of all stems on Pro, or on a song split with a credit), and a link that opens the song in StemConsole's practice room.

NameTypeReqDescription
split_idstringyesA split id from split_songs or list_my_songs.

No output schema declared.

No examples provided.

get_split_result ~67

Check the status of a split started by split_audio. Returns stem download URLs when status is done.

NameTypeReqDescription
download_keystring–The download_key returned by split_audio. Needed for the full-quality stem URLs.
job_idstringyesThe job_id returned by split_audio.

No output schema declared.

No examples provided.

get_task_url ~41

Return the StemConsole page URL for a specific audio task so you can hand the user a direct link.

NameTypeReqDescription
taskstringyesThe task to perform.

No output schema declared.

No examples provided.

list_my_songs ~32

The connected account's most recent songs (My songs), newest first, with split ids and practice-room links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_setlists ~24

The connected account's setlists, each with its songs and share link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rename_song ~47

Rename one of the connected account's songs in its library.

NameTypeReqDescription
namestringyes–
split_idstringyesA split id from split_songs or list_my_songs.

No output schema declared.

No examples provided.

split_audio ~221

Separate a song at a public URL into stems. This is a PAID action via x402, settled in USDC on Base Sepolia (testnet): call once WITHOUT `payment` to receive payment requirements, then call again WITH the x402 `payment` receipt to start the split. Returns a job_id; poll get_split_result for the stem URLs. If the paid endpoint is switched off, the call returns an error; people can split in the browser at https://stemconsole.ai/ instead.

NameTypeReqDescription
audio_urlstringyesPublic URL of the audio file to split.
filenamestring–Optional filename hint if the URL has no audio extension.
modelstring–vocals = Vocal Remover (2 stems: vocals, instrumental); fast = Basic Split (4 stems: vocals, drums, bass, other); full = Full Separation (6 stems, adds guitar and piano).
paymentstring–x402 payment payload (base64 X-PAYMENT). Omit on the first call to receive the payment requirements.

No output schema declared.

No examples provided.

split_songs ~157

Split 1 to 10 songs into stems on the connected StemConsole account, using its own plan and allowance, the same as splitting on the website. Give each song as a public audio URL (a direct file link; Dropbox and Google Drive share links work). One song starts at once and returns its split; 2 to 10 are queued as a batch that runs two at a time. Then poll get_split or get_batch until status is done. model: vocals = Vocal Remover (vocals, instrumental), fast = Basic Split (vocals, drums, bass, other), full = Full Separation (adds guitar and piano; Pro or a credit).

NameTypeReqDescription
modelstring––
songsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the StemConsole MCP server?

StemConsole is a hosted endpoint at https://stemconsole.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · stemconsole.ai

# add to Claude Code
claude mcp add --transport http ai-stemconsole-stemconsole 'https://stemconsole.ai/mcp'
Common questions

What is the StemConsole MCP server?

StemConsole is an MCP server listed in the public MCP registry as ai.stemconsole/stemconsole. Split songs into vocals, drums, bass, guitar and piano stems, in batches; manage songs and setlists. This page covers its hosted endpoint (https://stemconsole.ai/mcp).

Is the StemConsole MCP server safe to use?

StemConsole scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the StemConsole MCP server expose?

StemConsole exposes 13 tools: get_capabilities, get_task_url, split_audio, get_split_result, get_my_account, and 8 more. Their descriptions and schemas cost roughly 947 tokens of context every time the server is loaded.

Does the StemConsole MCP server require authentication?

No. We connected to StemConsole without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the StemConsole MCP server still maintained?

StemConsole is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.