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.

io.github.AudialAI/audial-mcp

PYPI · AUDIAL-MCP

Audial audio tools: stems, analysis, mastering, sample packs, MIDI, music generation, vocals.

Available components

−4 this week 80 Trust /100

Last scanned (5 hours ago)

Scores higher than 80% of PyPI servers

Category Design and Media

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3205 tokens (~200/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 148 → 200 ▼ functional
    • Package version: 0.1.1 → 0.5.0 functional
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 +1

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

  • 25 Oct 26 +1
    • Provenance: unverified → fail ▼ security
  • 24 Oct 26 0
    • Provenance: fail → unverified ▼ security
  • 23 Oct 26 +1

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

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 5 Nov 2026 · Analysed pypi/audial-mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 38 packages
Packages resolved 38
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~2,828 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
account ~45

Show whether this computer is signed in to Audial, and as whom. Use when a tool reports a credentials problem or the user asks which account is in use. Reads local settings only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
email–––
signed_inbooleanyes–
source––Where the credentials come from: 'sign-in' or 'api-key'.
summarystringyes–

No examples provided.

analyze ~122

Analyze a track: BPM, key, loudness and other characteristics. Use this first whenever the user asks for tempo, key or loudness. It is the fastest tool (seconds), does not count as a run, and changes nothing. The answer is in `metadata` and the same data is saved to the results folder.

NameTypeReqDescription
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

generate_midi ~123

Transcribe an audio file to MIDI. Use to get notes out of audio. On a full mix, run stem_split first and transcribe the stem you want. Counts as one run. MIDI files go to a new results folder; the source is unchanged.

NameTypeReqDescription
bpm––Override the detected tempo for note quantisation.
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

generate_music ~414

Generate music with the Audial music model. Text to music, covers, remixes, lego (re-render with one track emphasised), or analysis (understand). Use for new or transformed music, not to edit an existing mix: that is master or stem_split. Takes a few minutes and counts as one run, and audio goes to a new results folder.

NameTypeReqDescription
audio_cover_strength––0-1 fidelity to the original for cover/remix.
audio_duration––Length in seconds (10-600).
audio_formatstring–mp3, wav, flac, opus or aac.
batch_sizeinteger–Number of variations, 1-8.
bpm––Tempo hint in beats per minute.
instrumentalboolean–Generate without vocals.
key_scale––Key hint, e.g. 'G major'.
lyrics––Lyrics with optional section tags like [Verse] and [Chorus]. Omit for instrumental.
negative_prompt––What to avoid, comma-separated.
promptstringyesStyle description: genre, mood, instruments, vocal character. Tempo and key words in the prompt steer the model more than the numeric bpm/key fields, which are hints, not constraints.
reference_file––Local audio file; required for cover.
repainting_end––Remix end time in seconds (-1 = end).
repainting_start––Remix start time in seconds.
seed––Seed for reproducible output.
source_file––Local audio file; required for remix, lego, understand.
task_typestring–text2music (default), cover, remix, lego, or understand.
time_signature––e.g. '4/4'.
track_name––Track to emphasise for lego: vocals, drums, bass, guitar, piano, strings, synth, other.
vocal_languagestring–Language code for vocals, e.g. 'en'.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

generate_samples ~208

Extract a sample pack (one-shots and loops) from a track. Use when the user wants drum hits or loops taken from a finished track. Runs the `sample-pack` pipeline: splits stems, then builds the sample pack; one call, counted as one run. Tempo and key are detected automatically. Takes a few minutes and each step is reported as it starts and finishes. If the call times out the job keeps running: pipeline_status finds it. Samples go to a new results folder.

NameTypeReqDescription
components––Which components to sample, e.g. ['drums', 'bass'].
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
genre––Genre hint.
job_type––Sample pack job type accepted by Audial (default engine choice when omitted).
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

list_results ~86

List previous Audial results in the results folder, newest first. Use when the user asks where an earlier output went. Reads the local folder only: no account needed and nothing is sent anywhere.

NameTypeReqDescription
limitinteger–Maximum number of jobs to return, newest first.
tool––Filter by tool name, e.g. 'stem_split'. Omit for all tools.
NameTypeReqDescription
resultarrayyes–

No examples provided.

master ~131

Master a mix, optionally matching a reference track. Use for a finished stereo mix, not for separate stems. Pass a reference track when the user names one. Takes a few minutes and counts as one run. The master goes to a new results folder; the source is unchanged.

NameTypeReqDescription
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
reference_file––Optional reference track whose loudness and tone the master should match.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

pipeline_status ~83

Look up an Audial pipeline by id: its state, each step, and the outputs so far. Useful when a segment or generate_samples call timed out: the pipeline keeps running on Audial's side and this says how far it got.

NameTypeReqDescription
pipeline_idstringyesId of a pipeline, as returned in `execution_id` by segment or generate_samples.

Structured output declared, but exposes no named fields.

No examples provided.

segment ~202

Detect song sections (intro, verse, chorus...) and analyze components within them. Use for song structure. For tempo and key alone use analyze. Runs the `segmentation` pipeline: splits stems, then segments them; one call, counted as one run. Tempo and key are detected automatically. Takes a few minutes and each step is reported as it starts and finishes. If the call times out the job keeps running: pipeline_status finds it.

NameTypeReqDescription
analysis_type––Analysis type accepted by Audial's segmentation.
components––Components to analyze, e.g. ['vocals', 'drums'].
features––Features to compute per segment.
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
genre––Genre hint that improves section detection.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

service_status ~175

Which Audial tools have a worker awake right now, and what a cold one will cost. Audial's GPU workers scale to zero. A tool reported `warm: false` will spend `expectedColdStartMs` starting a worker before it does any work -- a few minutes, once -- on top of the job's own `expectedRunMs`. Worth checking before starting a long job, and worth telling the user about with the `notice` text when something is cold: otherwise the wait looks like a hang. Nothing here starts a job or costs anything.

NameTypeReqDescription
tool––Audial tool to report on: stem_split, analyze, segment, master, generate_samples, generate_midi, generate_music, sound2vital, sound2serum or text2vox. Omit for all of them.

Structured output declared, but exposes no named fields.

No examples provided.

sign_in ~67

Sign in to Audial through the user's browser. Opens an approval page and waits for it. Not needed before other tools: they start the same sign-in when nobody is signed in.

NameTypeReqDescription
switch_accountboolean–Sign out first and sign in again, to change or repair the account.
NameTypeReqDescription
email–––
signed_inbooleanyes–
source––Where the credentials come from: 'sign-in' or 'api-key'.
summarystringyes–

No examples provided.

sign_out ~54

Sign out of Audial on this computer and disconnect it from the account. Only when the user asks to sign out or switch accounts. The next job asks them to sign in again. Results already downloaded stay where they are.

Input schema present but exposes no named parameters.

NameTypeReqDescription
email–––
signed_inbooleanyes–
source––Where the credentials come from: 'sign-in' or 'api-key'.
summarystringyes–

No examples provided.

sound2serum ~171

Turn one isolated sound into an editable Xfer Serum 2 preset. Not for loops or melodies, which give a poor preset. If the result's summary says the match is weak, tell the user and suggest trimming the input to one note.

NameTypeReqDescription
file_pathstringyesOne isolated sound: a single note, chord stab or hit, ideally 1-4 s and dry, 20 s at most. Not a loop, melody, drum pattern or anything with several notes in sequence: those produce a poor preset eve…
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

sound2vital ~152

Turn one isolated sound into an editable Audial Synth preset. Not for loops or melodies, which give a poor preset. If the result's summary says the match is weak, tell the user and suggest trimming the input to one note.

NameTypeReqDescription
file_pathstringyesOne isolated sound: a single note, chord stab or hit, ideally 1-4 s and dry, 20 s at most. Not a loop, melody, drum pattern or anything with several notes in sequence: those produce a poor preset eve…
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

stem_split ~227

Split a track into separate instrument stems, optionally retimed and rekeyed. Use for a full song or mix when the user wants vocals, drums, bass or an instrumental on their own. For tempo and key alone use analyze; for sections use segment. Takes a few minutes and counts as one run. Stems go to a new results folder; the source is unchanged.

NameTypeReqDescription
algorithmstring–Separation algorithm. Default 'primaudio'.
file_pathstringyesFull path to a local audio file (.wav, .mp3, .aif, .aiff, .flac, .m4a, .ogg, .aac). ~ is expanded.
stems––Stems to extract from: vocals, drums, bass, other, full_song_without_vocals. Default: vocals, drums, bass, other.
target_bpm––Retime the stems to this tempo (beats per minute).
target_key––Transpose the stems to this key, e.g. 'A minor' or 'F# major'.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

text2vox ~568

Synthesize a sung vocal (and MIDI) from lyrics, a melody and a reference voice. Needs both a reference clip of the voice and a melody, as MIDI or audio. lyrics_mode decides how the lyrics are lined up with the melody's notes; "per_note" is the one that gives exact control. See the lyrics_mode and lyrics descriptions. Takes a few minutes and counts as one run. Audio and MIDI go to a new results folder.

NameTypeReqDescription
bend_smoothing_ms––Pitch-bend smoothing window in ms.
cfg_strength––Guidance strength.
leading_silence_s––Silence before the first note, seconds.
lyricsstringyesLyrics to sing. With lyrics_mode 'per_note' this is pipe-delimited, one token per MIDI note, e.g. 'amazing|-|-|grace|-|how|sweet|the|sound'; otherwise it is ordinary text.
lyrics_modestring–How the lyrics line up with the melody. 'auto' (default): ordinary text, one word per MIDI note, aligned for you (word_timestamps_file helps). '1to1': the text is passed to the synthesizer untouched.…
melody_audio_file––Audio whose melody is transcribed and followed, if no MIDI.
midi_file––MIDI melody (.mid). Give this or melody_audio_file.
nfe_steps––Synthesis steps; more is slower and cleaner.
no_pitch_bends––Disable pitch bends.
pitch_shift––Semitones to shift the melody.
reference_filestringyesShort clip of the reference voice (timbre).
reference_text––Transcript of the reference clip, if known.
seed––Seed for reproducible output.
strict_pitch––Force exact pitch to the melody.
word_timestamps_file––Optional JSON word timings.
NameTypeReqDescription
execution_id–yes–
filesarrayyes–
metadataobjectyes–
output_dirstringyes–
summarystringyes–
toolstringyes–

No examples provided.

Install

How do I install the io.github.AudialAI/audial-mcp server?

io.github.AudialAI/audial-mcp runs locally as a PyPI package, launched with uvx audial-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · audial-mcp

# add to Claude Code
claude mcp add audialai-audial-mcp -- uvx audial-mcp
Common questions

What is the io.github.AudialAI/audial-mcp server?

io.github.AudialAI/audial-mcp is listed in the public MCP registry as io.github.AudialAI/audial-mcp. Audial audio tools: stems, analysis, mastering, sample packs, MIDI, music generation, vocals. This page covers its PyPI package (audial-mcp).

Is the io.github.AudialAI/audial-mcp server safe to use?

io.github.AudialAI/audial-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.AudialAI/audial-mcp server expose?

io.github.AudialAI/audial-mcp exposes 16 tools: stem_split, analyze, segment, master, generate_samples, and 11 more. Their descriptions and schemas cost roughly 2,828 tokens of context every time the server is loaded.

Is the io.github.AudialAI/audial-mcp server still maintained?

io.github.AudialAI/audial-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.AudialAI/audial-mcp server under?

io.github.AudialAI/audial-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.