tools.audiolab/audiolab
NPM · @AUDIOLABTOOLS/MCP-SERVER · SCANNED OCT 1
Loudness (EBU R128 / BS.1770-4), true-peak and voice-quality analysis for local files and URLs.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1851 tokens (~185/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the tools.audiolab/audiolab MCP server?
tools.audiolab/audiolab runs locally as an npm package, launched with npx -y @audiolabtools/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @audiolabtools/mcp-server
claude mcp add tools-audiolab-audiolab -- npx -y @audiolabtools/mcp-server
{
"mcpServers": {
"tools-audiolab-audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
]
}
}
} {
"servers": {
"tools-audiolab-audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
]
}
}
} codex mcp add tools-audiolab-audiolab -- npx -y @audiolabtools/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tools-audiolab-audiolab": {
"type": "local",
"command": [
"npx",
"-y",
"@audiolabtools/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add tools-audiolab-audiolab --command npx --arg -y --arg @audiolabtools/mcp-server
mcp_servers:
tools-audiolab-audiolab:
command: "npx"
args: ["-y", "@audiolabtools/mcp-server"] {
"McpServers": {
"tools-audiolab-audiolab": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@audiolabtools/mcp-server"
]
}
}
} assistant mcp add tools-audiolab-audiolab -t stdio -c npx -a -y @audiolabtools/mcp-server
{
"mcpServers": {
"tools-audiolab-audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
]
}
}
} 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.
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Sept 26 0
- Package version: 0.4.0 → 0.4.1 functional
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 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.
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 1 Oct 2026 · Analysed npm/@audiolabtools/mcp-server@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_batch Batch: one analysis route over many files ~256
Run one analysis route over up to 20 audio sources in a single call. Returns per-item ok/data/error; each item is metered as one call. Routes: mixlab/analyze (default), mixlab/check-target, mixlab/timeseries, mixlab/spectrum, voicelab/qa, voicelab/segments, signallab/index. Use for folder QA, library indexing, or checking a whole release against a loudness target. Sources: public https urls and/or local file paths.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | Analysis route to run for every item (default mixlab/analyze). |
| lufs | number | – | For target="custom": integrated LUFS target. |
| paths | array | – | LOCAL audio file paths; each uploads over a one-shot signed URL, is analysed, then deleted. Combined max 20 items with urls. |
| target | string | – | For mixlab/check-target: preset id (spotify, ebu-broadcast, podcast, …) or "custom". |
| tp | number | – | For target="custom": max true-peak (dBTP). |
| urls | array | – | Public https URLs to audio files. Combined max 20 items with paths. |
No output schema declared.
No examples provided.
analyze_loudness Analyze loudness (MixLab) ~154
Loudness and dynamics for a track: integrated LUFS (EBU R128 / BS.1770-4), true-peak (dBTP), loudness range (LRA), crest factor, stereo correlation, mono compatibility, and tonal balance. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
analyze_profile Analyse against a profile ~327
Measure a file against a named working set of lenses and get back only what that question needs. Profiles: voice (is this take usable, and which phrase is the problem), master (will this translate to real platforms and speakers), provenance (what has been done to this file, and is it all one source), dataset (which of these files are good enough, and why not the rest), environment (what is in this space, and what kind of noise is it), broadcast (does this file meet the delivery spec), loop (is this loop clean, on the grid, and safe to drop in a DAW). basic is the free tier; the other seven need a paid plan. Results are keyed by stable lens id. Only the analysis passes the profile needs are run. Set series:true to also get the curves, the per-block lanes and the per-phrase values,a much larger payload, so leave it off unless you are going to read them. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| profile | string | yes | Which question to answer. |
| series | boolean | – | Include time series, per-block lanes and per-phrase arrays. Off by default. |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
analyze_timeseries Loudness over time (for graphing / visualization) ~164
Short-term LUFS samples over time (EBU R128, ~3s window) with their time-base, plus downsampled waveform peaks. Arrays suitable for loudness-over-time charts, level meters, and waveform UIs. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
| waveformPoints | integer | – | Waveform peak count (default 200). |
No output schema declared.
No examples provided.
analyze_voice Analyze voice quality (VoiceLab) ~144
Speech-quality QA for a voice recording: speech/silence ratio, speaking-rate label, signal-to-noise, noise floor, room-echo label, sibilance risk, clipping severity. Gates a voice take. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
check_target Check audio against a loudness target (Spotify, EBU, etc.) ~217
Verify whether audio hits a delivery target (Spotify -14 LUFS / EBU broadcast -23 / podcast -16 / etc.). Returns pass/fail with per-metric deltas and a concrete ffmpeg loudnorm command to fix if failing. Presets: spotify, apple-music, youtube, tidal, amazon-music, podcast, ebu-broadcast, atsc-broadcast; or target="custom" with lufs+tp. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| lufs | number | – | – |
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| target | string | yes | Preset id or "custom". |
| tp | number | – | – |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
compare_loudness Compare two tracks (A/B) ~137
Run loudness analysis on TWO sources and return both results for an A/B comparison: master vs reference, before vs after a fix, two encoders, two cuts. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| pathA | string | – | First source as a local file path. |
| pathB | string | – | Second source as a local file path. |
| urlA | string | – | First source URL (e.g. master). Provide urlA or pathA. |
| urlB | string | – | Second source URL (e.g. reference). Provide urlB or pathB. |
No output schema declared.
No examples provided.
get_spectrum FFT spectrum data ~158
Frequency-domain magnitude data (paired frequency/magnitude arrays) plus energies in 7 standard bands (sub/bass/lowMid/mid/highMid/presence/air). There is no dominant-band field in the response. For spectrum-analyzer UIs and tonal-balance analysis. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
get_speech_segments Speech segments (VoiceLab) ~141
List voiced speech regions with start/end timestamps and per-segment RMS. For auto-trim, chapter generation, and speaker-turn detection. RMS-based voice-activity detection, not speaker diarization. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
index_signal Index a signal (SignalLab) ~153
A metadata index for any audio file: content-type guess (voice/music/mixed/noise/silence) with confidence, brightness & dynamics buckets, dominant band, clipping/silence regions, and tag suggestions. For triage or auto-tagging a library. Audio source: a public https URL, or a local file path (`path`).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or p… |
| url | string | – | Public https URL to the audio file. Provide exactly one of url or path. |
No output schema declared.
No examples provided.
What is the tools.audiolab/audiolab MCP server?
tools.audiolab/audiolab is an MCP server listed in the public MCP registry as tools.audiolab/audiolab. Loudness (EBU R128 / BS.1770-4), true-peak and voice-quality analysis for local files and URLs. This page covers its npm package (@audiolabtools/mcp-server).
Is the tools.audiolab/audiolab MCP server safe to use?
tools.audiolab/audiolab scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. 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 tools.audiolab/audiolab MCP server expose?
tools.audiolab/audiolab exposes 10 tools: analyze_loudness, check_target, analyze_timeseries, get_spectrum, analyze_voice, and 5 more. Their descriptions and schemas cost roughly 1,851 tokens of context every time the server is loaded.
Is the tools.audiolab/audiolab MCP server still maintained?
tools.audiolab/audiolab is still listed as active in the MCP registry. We last reached this channel on 1 October 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 tools.audiolab/audiolab MCP server under?
tools.audiolab/audiolab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.