Supadata vs music-metadata-mcp
Supadata is an MCP server published by supadata-ai. Marketplaces we read that list it: 2 (Docker MCP Catalog, Official MCP Registry). music-metadata-mcp is an MCP server published by stevebirring-star. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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 |  Supadata |  music-metadata-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1dc20c9a8a2b Forks (GitHub): 10 Stars (GitHub): 63 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 1.3.6 Forks (GitHub): 10 Stars (GitHub): 63 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.20.2 Downloads/month (npm): 1 517 Downloads/week (npm): 344 Forks (GitHub): 0 Stars (GitHub): 3 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 | Supadata | music-metadata-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 63 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 10 (better) | 0 (worse) |
| Last release (differs) | 2026-11-05 (worse) | 2026-11-09 (better) |
| Where it runs (differs) | Remote server or your machine | On your machine (music-metadata-mcp) |
| Transport (differs) | stdio, Streamable HTTP | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/supadata-ai/mcp | github.com/stevebirring-star/music-metadata-mcp |
| Changes in the last 7 days (differs) | 1 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Responded 3 h ago, requires authentication | no remote endpoint we check |
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
Supadata
Official Supadata MCP Server - Adds powerful video & web scraping to Cursor, Claude and any other LLM clients.
music-metadata-mcp
MCP server for the FreqBlog Music API — 25 tools covering audio features, plain-language search by description, seedless discovery by tempo/key/genre/year, similar-sounding tracks from several seeds, honestly-labelled tags, recommendations (Spotify /recom
How to run each
Supadata As a local MCP server: Docker image
claude mcp add --env "SUPADATA_API_KEY=<YOUR_SUPADATA_API_KEY>" --transport stdio supadata -- docker run -i --rm -e SUPADATA_API_KEY ghcr.io/supadata-ai/mcpRequires: SUPADATA_API_KEY (secret)
music-metadata-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Supadata has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of music-metadata-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of music-metadata-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Supadata · What it can do: music-metadata-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.