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/mcp-tool-shop-org/mcp-voice-soundboardWrote 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/mcp-tool-shop-org/mcp-voice-soundboard/voice-soundboard)<a href="https://agentmods.dev/mcp/mcp-tool-shop-org/mcp-voice-soundboard/voice-soundboard"><img src="https://agentmods.dev/badge/mcp/mcp-tool-shop-org/mcp-voice-soundboard/voice-soundboard/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/mcp-tool-shop-org/mcp-voice-soundboard/voice-soundboard"><img src="https://agentmods.dev/badge/mcp/mcp-tool-shop-org/mcp-voice-soundboard/voice-soundboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
voice-soundboard 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
{
"voice-soundboard": {
"command": "npx",
"args": [
"-y",
"@mcptoolshop/voice-soundboard-mcp"
],
"env": {}
}
}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 · 10 lines scan A 5d385251c431
voice-soundboard is an MCP server published in the GitHub repository mcp-tool-shop-org/mcp-voice-soundboard (0 stars, last pushed 8d 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
omnivoice
OmniVoice: Towards Omnilingual Zero-Shot Text-to-Speech with Diffusion Language Models. Runs locally from the omnivoice Python package.
noisy-coding
MCP server "noisy-coding" as configured in noisy/noisy-coding. Runs in Docker (docker.io/noisy/noisy-coding:2.13.3). Needs 1 environment variable to run.
voice-bridge
Multi-engine TTS for AI coding assistants. 5 engines, free engine included. Runs locally from the ai-voice-bridge npm package.
punt-langlearn-tts
TTS MCP server and CLI for language learning (ElevenLabs, AWS Polly, OpenAI). Runs locally from the punt-langlearn-tts Python package.
speak-aloud
MCP server "speak-aloud" as configured in tsuru0805/speak-aloud-mcp. Launched with speak-aloud-mcp. Needs 4 environment variables to run.
not-happy-jan
MCP server "not-happy-jan" as configured in guruswami-ai/not-happy-jan. Runs locally from the not-happy-jan Python package.