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/brian-mwirigi/aux-mcpWrote 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/brian-mwirigi/aux-mcp/spotify-aux)<a href="https://agentmods.dev/mcp/brian-mwirigi/aux-mcp/spotify-aux"><img src="https://agentmods.dev/badge/mcp/brian-mwirigi/aux-mcp/spotify-aux/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/brian-mwirigi/aux-mcp/spotify-aux"><img src="https://agentmods.dev/badge/mcp/brian-mwirigi/aux-mcp/spotify-aux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spotify-aux 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 11d 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
{ "spotify-aux": { "command": "npx", "args": [ "-y", "spotify-aux" ] } }
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.
- 11d ago First seen · 9 lines scan A 104f8df3e171
spotify-aux is an MCP server published in the GitHub repository brian-mwirigi/aux-mcp (1 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
kinocut
Trusted, guardrailed video editing for AI agents. FFmpeg, Hyperframes, repurposing tools, Python client, CLI, and MCP server. Runs locally from the kinocut Python package.
prompt-to-asset
Generate app icons, favicons, OG images, and logos by routing across 30+ image models. Runs locally from the prompt-to-asset npm package.
imagine-mcp
MCP server for image/video understanding & generation (Gemini/OpenAI/Grok). Runs locally from the imagine-mcp Python package. Needs 4 environment variables to run.
image-video
Generate images, video & speech with Nano Banana, Veo, Omni and Gemini TTS. Pay as you go. Remote server at bananabanana.pro.
presentation-md
MCP server exposing all 14 presentation-md tools (render/export/audit/judge/scaffold/share/deploy/import/preview) to any MCP-compatible AI agent. Runs locally from the @presentation-md/mcp-server npm package.
spotify-mcp
MCP server "spotify-mcp" as configured in martin-gomola/spotify-mcp. Launched with bash -lc repo="${SPOTIFY_MCP_REPO:-$HOME/dev/spotify-mcp}"; cd "$repo" 2>/dev/nu.