Spotify Trends API vs io.github.mrfentmen/openwhyd-mcp
Spotify Trends API is an MCP server published by trendsapi.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/openwhyd-mcp is an MCP server published by mrfentmen. 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 |   Spotify Trends API | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 415 Downloads/week (npm): 60 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 | Spotify Trends API | io.github.mrfentmen/openwhyd-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Remote server (spotify.api.trendsapi.ai/mcp) | On your machine (openwhyd-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/trendsapi-ai/trends-mcp | github.com/mrfentmen/openwhyd-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 30 h ago returned HTTP 405 | 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
Spotify Trends API
Spotify top podcast trends and listening signals. Free key at trendsapi.ai
io.github.mrfentmen/openwhyd-mcp
Hot tracks and trending music from OpenWhyd. No key required.
How to run each
Spotify Trends API As a remote MCP server
claude mcp add --transport http spotify https://spotify.api.trendsapi.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.mrfentmen/openwhyd-mcp As a local MCP server: npm package
claude mcp add --transport stdio openwhyd-mcp -- npx -y openwhyd-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Spotify Trends API 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: Spotify Trends API · What it can do: io.github.mrfentmen/openwhyd-mcp · Compare two other plugins
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.