music-catalog-diligence vs TIDAL MCP
music-catalog-diligence is a plugin bundle for AI coding tools published by recoupable. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). TIDAL MCP is an MCP server published by sickn33. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  music-catalog-diligence |  TIDAL MCP |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 1 187 Downloads/week (npm): 69 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | music-catalog-diligence | TIDAL MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@sickn33/tidal-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 22 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/recoupable/music-catalog-diligence | github.com/sickn33/tidal-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
music-catalog-diligence
Music Catalog Diligence helps catalog buyers, sellers, and financing teams review music catalog deals faster and with better evidence. It turns messy data rooms into source-cited workpapers by normalizing royalty statements, checking rights and metadata gaps, analyzing NPS/NLS, flagging diligence risks, and preparing buyer, seller, or lender-ready deal packages.
TIDAL MCP
Search, analyze, organize, and safely modify TIDAL through 122 typed MCP tools.
How to run each
music-catalog-diligence As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install music-catalog-diligence@claude-communityTIDAL MCP As a local MCP server: npm package
claude mcp add --transport stdio tidal-mcp -- npx -y @sickn33/tidal-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of music-catalog-diligence publish no settings it asks for, so we do not compare settings.
What it can do: music-catalog-diligence · What it can do: TIDAL MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.