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/daredoole/audio-calibration-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/daredoole/audio-calibration-mcp/audio-calibration)<a href="https://agentmods.dev/mcp/daredoole/audio-calibration-mcp/audio-calibration"><img src="https://agentmods.dev/badge/mcp/daredoole/audio-calibration-mcp/audio-calibration/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/daredoole/audio-calibration-mcp/audio-calibration"><img src="https://agentmods.dev/badge/mcp/daredoole/audio-calibration-mcp/audio-calibration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
audio-calibration 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
{
"audio-calibration": {
"command": "node",
"args": [
"./dist/server.mjs"
],
"cwd": ".",
"env": {
"AUDIO_REW_URL": "http://127.0.0.1:4735"
}
}
}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 · 12 lines scan A beb4e27f4799
audio-calibration is an MCP server published in the GitHub repository daredoole/audio-calibration-mcp (7 stars, last pushed yesterday), 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
evoburrow-mcp
MCP server "evoburrow-mcp" as configured in daredoole/evoburrow-mcp. Launched with https://github.com/daredoole/evoburrow-mcp/releases/download/v2.0.0-beta.1/evobu.
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.
a1-evo-audio-expert
MCP server "a1-evo-audio-expert" as configured in daredoole/evoburrow-mcp. Runs ./dist/server.mjs with node.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.