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.01091 |
| Opus 5.5 | $0.00015 | $0.00436 |
| Sonnet 5.5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
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 16d 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 — 81 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 current in-repo and live-protocol evidence first, then web research. Never assert conformance or inventory from memory.
Current default production baseline: 562 tools, 17 fixed resources, 28 resource templates, and 14 prompts. Regenerate with npm run count:tools -- --write; never substitute historical prose.
Steps
-
Establish the current protocol surface.
- Read
package.jsonfor the MCP SDK dependency and the scripts/entry surface; readsrc/index.tsfor the actual transport and tool/resource/ prompt registration gates. - Treat
SPEC.mdas design/history, not a count source. Static registration searches miss factories, inline registrations, scope gates, and toolset trimming. - Connect to the current server and record the live results of
tools/list,resources/list,resources/templates/list, andprompts/list. For tools,toolset_report.structuredContentexposesregistered_tools,active_toolsets, andactive_modules. - Cite
tests/mcp.smoke.test.ts: it starts the real stdio entry and exchanges newline-delimited JSON-RPC for initialize and primitive lists. - Criterion: every count and primitive claim names the live request or
source file inspected for this comparison. Never copy a count from
CHANGELOG.md,SPEC.md, or an earlier answer.
- Read
-
Re-audit optional or unsupported protocol features from current source. Put the proof beside every claim:
Claim Current proof to inspect stdio transport src/index.tsimports and connectsStdioServerTransport; no HTTP/SSE server entry is wired thereOAuth is Authorization Code + PKCE, not server-side dynamic client registration src/auth.tsbuilds an authorization request withcode_challenge_method=S256and exchangesauthorization_codepluscode_verifierresource argument completion is present src/resources/templates.tsattachescomplete.idto thespotify://show/{id},spotify://episode/{id}andspotify://audiobook/{id}templates;tests/resources.templates.test.tsexercises the show and episode suggestersno roots/sampling feature is exposed Search src/for roots and sampling handlers and confirm no implementation; describe these as client capabilities that this server does not consume, not as a conformance failure
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.
- 16d ago Changed 92a553fc53f8
- 28d ago Changed · +3 lines 00f4a2755691
- 29d ago Changed 5b09ba177a2d
- 1mo ago Changed · +44 lines a71c466da2f7
- 1mo ago Changed 35bba3d26e7d
- 1mo 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 3d ago), licensed MIT. It adds 37 tokens to every session and 1,091 once invoked, about $0.0001 per session on Opus 5.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
local-delegation
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…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
install-image-search-mcp
Install and configure the Serbyte Image Search MCP server for Unsplash, Pexels, and Pixabay. Use when a user asks an AI coding agent to install this MCP, add it to an MCP client, configure provider API keys, or verify the installation.
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).
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.