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.
git clone --depth 1 https://github.com/flujo-app/mcp-audio-studio-mcpappWrote 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/flujo-app/mcp-audio-studio-mcpapp/mcp-audio-studio)<a href="https://agentmods.dev/mcp/flujo-app/mcp-audio-studio-mcpapp/mcp-audio-studio"><img src="https://agentmods.dev/badge/mcp/flujo-app/mcp-audio-studio-mcpapp/mcp-audio-studio/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/flujo-app/mcp-audio-studio-mcpapp/mcp-audio-studio"><img src="https://agentmods.dev/badge/mcp/flujo-app/mcp-audio-studio-mcpapp/mcp-audio-studio.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-audio-studio 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 10d 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
{
"mcp-audio-studio": {
"command": "npx",
"args": [
"-y",
"mcp-audio-studio"
],
"env": {
"MCP_AUDIO_STUDIO_DATA": ""
}
}
}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.
- 10d ago First seen · 12 lines scan A 60abf3cedf5e
mcp-audio-studio is an MCP server published in the GitHub repository flujo-app/mcp-audio-studio-mcpapp (0 stars, last pushed 4d 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
notify-mcp
MCP server for built-in audio playback and desktop notifications. Runs locally from the @zakotoys/notify-mcp npm package.
sticker-mcp
MCP server "sticker-mcp" as configured in asashiki/sticker-mcp. Runs locally from the @asashiki/sticker-mcp npm package.
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.
behringer-wing-mcp
MCP server "behringer-wing-mcp" as configured in ralfferreira/behringer-wing-mcp. Runs locally from the behringer-wing-mcp npm package.
starsinger-mcp
MCP server for StarSinger AI music catalog — search, stream & browse AI-generated tracks. Runs locally from the starsinger-mcp npm package. Needs 2 environment variables to run.
mcp-use-docs
MCP server "mcp-use-docs", hosted remotely at manufact.com, as configured in mcp-use/mcp-use.