Ext Ops Panel
Open dashboard
Comparison

music-catalog-diligence vs Magic Master — Audio Mastering

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). Magic Master — Audio Mastering is an MCP server published by magicmaster.pro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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

Where each is published
Marketplacemusic-catalog-diligenceMagic Master — Audio Mastering
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: 0.5.0
Downloads/month (npm): 153
Downloads/week (npm): 43
Forks (GitHub): 0
Stars (GitHub): 2
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

music-catalog-diligence vs Magic Master — Audio Mastering
Factmusic-catalog-diligenceMagic Master — Audio Mastering
Marketplaces that list it11
Stars (GitHub)22
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (magicmaster.pro/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)22Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/recoupable/music-catalog-diligencegithub.com/denisok-ai/magicmaster-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 24 h ago

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

In its own words, on Claude Code: claude-plugins-community:

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.

Magic Master — Audio Mastering

In its own words, on Official MCP Registry:

Audio mastering for AI agents: LUFS/True Peak targets, Suno/Udio AI-fingerprint removal.

How to run each

music-catalog-diligence As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install music-catalog-diligence@claude-community

Magic Master — Audio Mastering As a remote MCP server

Claude Code
claude mcp add --transport http mastering https://magicmaster.pro/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Magic Master — Audio Mastering has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: music-catalog-diligence · What it can do: Magic Master — Audio Mastering · 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.

Where the data comes from: how the catalog is built