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.
npx skills add NovaLux12/spotify-mcp-server --skill spotify-mcp-competitor-comparisongit clone --depth 1 https://github.com/NovaLux12/spotify-mcp-serverWrote 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/skills/novalux12/spotify-mcp-server/spotify-mcp-competitor-comparison)<a href="https://agentmods.dev/skills/novalux12/spotify-mcp-server/spotify-mcp-competitor-comparison"><img src="https://agentmods.dev/badge/skills/novalux12/spotify-mcp-server/spotify-mcp-competitor-comparison/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/skills/novalux12/spotify-mcp-server/spotify-mcp-competitor-comparison"><img src="https://agentmods.dev/badge/skills/novalux12/spotify-mcp-server/spotify-mcp-competitor-comparison.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00746 |
| Opus 5 | $0.00018 | $0.00373 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
spotify-mcp-competitor-comparison 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spotify MCP Competitor Comparison
Answer "is our MCP really standard / do others offer more" or "are we better than X" questions with in-repo evidence first, then web research. Never assert conformance from memory — the repo holds the proof.
Steps
-
Verify protocol conformance in-repo before any web search.
- Read SPEC.md §2 (Transport, Stack) and §4.0.2 (MCP server wiring) for SDK version, transport, and primitive registration.
- Grep src/ for the primitive surface:
server.tool(/server.prompt(/server.resource(counts, andstructuredContent, progress-notification usage.structuredContentemission lives in src/shaping.ts plus tools like playlistmisc.ts, searchhistory.ts, queueops.ts. - Cite tests/mcp.smoke.test.ts: it spawns the real entry over stdio and speaks raw newline-delimited JSON-RPC (initialize / tools/list / prompts/list / resources/list), so protocol conformance is tested, not assumed.
- Read current tool/prompt/resource counts from CHANGELOG or
grep -rn "server\.tool\|registerTool" src --include="*.ts" | wc -lwith typed-search factory correction (545 - 1 + 7 = 551) / livetools/list— they drift between releases (e.g., 551 tools as of v1.27.1 vs 550 in CHANGELOG at ee814a2); never hardcode counts from an older answer. - Criterion: every protocol claim (SDK, transport, primitive counts, spec features) is backed by a file/line you inspected this turn.
-
State optional spec features the server lacks as optional, not gaps.
- Fixed checklist: stdio-only transport (no HTTP/SSE/Streamable), no server-side OAuth 2.0 dynamic client registration (PKCE CLI flow instead), no
completions/complete, no roots/sampling. - Criterion: the answer lists gaps only from this checklist and marks each as an optional spec feature, not a conformance failure.
- Fixed checklist: stdio-only transport (no HTTP/SSE/Streamable), no server-side OAuth 2.0 dynamic client registration (PKCE CLI flow instead), no
-
Survey the landscape with web_search.
- Query patterns: " spotify-mcp npm tools", "most popular spotify mcp server stars", " spotify mcp".
- Tabulate each competitor's tool count or documented scope from search snippets/docs (e.g., SpotifyMCP2 docs state "eight tools").
- Check whether an official Spotify-published MCP server exists before claiming absence; if you find only community servers, say so explicitly.
- Criterion: every competitor row cites a source from search results plus a tool count or documented scope; the "official server exists?" claim is verified, not assumed.
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.
- 6d ago Changed 35bba3d26e7d
- 10d ago First seen · 34 lines · 37 tokens per session scan A a95fb32934e2
spotify-mcp-competitor-comparison is a skill published in the GitHub repository NovaLux12/spotify-mcp-server (1 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 746 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
business-model-validator
Use when a prospect, new customer, or existing operator wants to know whether Zooza fits their business, or which Zooza features map to how they operate. No Zooza account required — works as a pure knowledge interview.
delegacion-local
Regla y catálogo para delegar pasos mecánicos (resumir, clasificar, extraer, boilerplate, mensaje de commit desde un diff, traducir texto o archivo, resumir salida de lint/tests/CI, explicar código, describir una imagen, verificar si el backend local está disponible) a modelos locales vía las tools local del MCP…
@elad12390/web-research-assistant
Comprehensive MCP server for web research with 14 tools: SearXNG + Exa AI search, URL crawling, stealth scraping (Cloudflare bypass), package registry lookup (npm/PyPI/crates), GitHub stats, changelog fetching, tech comparison, error translation, API docs discovery, stock image search, and service health. Trigger…
negotiate-terminology
Use when the user wants to set up their business vocabulary — what they call programmes, classes, sessions, trainers. Also use when the user says "you're using the wrong words" or this is their first session with Zooza MCP.
class-management
Use when the user wants to create a new class, group, or course in Zooza — e.g. "set up a Monday yoga class", "add a new group", "schedule a course". Guides through programme selection, venue, trainer, session pattern, and commits.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).