Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/audio-launch/audiolab-mcp-server/audiolabgit clone --depth 1 https://github.com/Audio-Launch/audiolab-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/audio-launch/audiolab-mcp-server/audiolab)<a href="https://agentmods.dev/mcp/audio-launch/audiolab-mcp-server/audiolab"><img src="https://agentmods.dev/badge/mcp/audio-launch/audiolab-mcp-server/audiolab.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
audiolab scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
],
"env": {
"AUDIOLAB_API_KEY": "",
"AUDIOLAB_API_BASE": "",
"AUDIOLAB_TIMEOUT_MS": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 14 lines scan A dadce4457183
audiolab is an MCP server published in the GitHub repository Audio-Launch/audiolab-mcp-server (0 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
loudcheck
Loudness compliance verdicts against formal published standards (EBU R128, ATSC A/85) — a pass/fail answer with exact deltas, not raw meter output. Runs locally from the loudcheck Python package.
cochlea-mcp
MCP server "cochlea-mcp" as configured in richer-richard/cochlea. Launched with https://github.com/richer-richard/cochlea/releases/download/cochlea-mcp-v0.7.0/c.
mcp-listen
Give your AI agents the ability to listen. Microphone capture and speech-to-text. Runs locally from the mcp-listen npm package.
augent
MCP server "augent" as configured in AugentDevs/augent. Launched with augent-mcp.
mixx-dj-mcp
MCP server "mixx-dj-mcp" as configured in sandraschi/mixx-dj-mcp. Launched with https://github.com/sandraschi/mixx-dj-mcp/releases/download/v0.2.0/mixx-dj-mcp-v.
flstudio-mcp
AI-powered FL Studio control via MCP - mixing, composition, plugin control, and mix diagnosis through natural language. Runs locally from the fl-studio-mcp Python package.