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/vecnode/dawmcpWrote 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/vecnode/dawmcp/audacity)<a href="https://agentmods.dev/mcp/vecnode/dawmcp/audacity"><img src="https://agentmods.dev/badge/mcp/vecnode/dawmcp/audacity/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/vecnode/dawmcp/audacity"><img src="https://agentmods.dev/badge/mcp/vecnode/dawmcp/audacity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
audacity 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 1mo 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
{
"audacity": {
"command": "cargo",
"args": [
"run",
"--release",
"-p",
"dawmcp-server",
"--",
"--daw=audacity"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 13 lines scan A b4cfd5b13db1
audacity is an MCP server published in the GitHub repository vecnode/dawmcp (0 stars, last pushed 3mo 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
memscope-mcp
AI-native memory research MCP server for reverse engineering. Runs locally from the memscope-mcp Python package.
assetto-mcp
MCP server "assetto-mcp" as configured in mishan/assetto-mcp. Runs locally from the assetto-mcp Python package.
studio-pro-mcp
MCP server "studio-pro-mcp" as configured in pajdarova/FenderStudioProMCP. Runs locally from the studio-pro-mcp Python package.
orpheus
Visual UI snip tool for A/B variant generation — drag to select a component, get design variants instantly. Runs locally from the orpheus-mcp Python package.
pampapilot
MCP server "pampapilot" as configured in LeoLisena/pampa-pilot. Runs locally from the pampapilot Python package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.