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/pajdarova/FenderStudioProMCPWrote 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/pajdarova/fenderstudiopromcp/studio-pro-mcp)<a href="https://agentmods.dev/mcp/pajdarova/fenderstudiopromcp/studio-pro-mcp"><img src="https://agentmods.dev/badge/mcp/pajdarova/fenderstudiopromcp/studio-pro-mcp/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/pajdarova/fenderstudiopromcp/studio-pro-mcp"><img src="https://agentmods.dev/badge/mcp/pajdarova/fenderstudiopromcp/studio-pro-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
studio-pro-mcp 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 9d 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
{ "studio-pro-mcp": { "command": "uvx", "args": [ "studio-pro-mcp" ] } }
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.
- 9d ago First seen · 8 lines scan A ea6fa8e38db5
studio-pro-mcp is an MCP server published in the GitHub repository pajdarova/FenderStudioProMCP (0 stars, last pushed 1mo 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
mcp-music-studio
Music studio: ABC notation composition and Strudel live coding with ext-apps UI. Runs locally from the mcp-music-studio npm package.
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.
mcp-lyricscom
Search song lyrics on lyrics.com by word or by title, and fetch full lyrics. No API key required. Runs locally from the mcp-lyricscom npm package. Needs 3 environment variables to run.
king-crimson-mcp
An MCP server for King Crimson discography and live-performance history, with a curated line-up-era (incarnation) model. Runs locally from the king-crimson-mcp Python package. Needs 3 environment variables to run.
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.
audacity
MCP server "audacity" as configured in vecnode/dawmcp. Launched with cargo run --release -p dawmcp-server -- --daw=audacity.