mcp-registry/com.freqblog/music-metadata/get_audio_features / alternatives
mcp-registry/com.freqblog/music-metadata/get_audio_featuresThe best live alternatives to mcp-registry/com.freqblog/music-metadata/get_audio_features right now are mcp-registry/io.github.pipeworx-io/spotify/get_audio_features, mcp-registry/io.github.pipeworx-io/spotify/get_track, mcp-registry/io.github.pipeworx-io/openverse/get_audio, mcp-registry/com.adbutler/mcp-server/get_audio_creative, pulsemcp/adbutler/get_audio_creative — capability-matched and ranked by current reliability. mcp-registry/com.freqblog/music-metadata/get_audio_features itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/spotify/get_audio_features is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/spotify/get_track, mcp-registry/io.github.pipeworx-io/openverse/get_audio, mcp-registry/com.adbutler/mcp-server/get_audio_creative, pulsemcp/adbutler/get_audio_creative. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.freqblog/music-metadata/get_audio_features's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.freqblog%2Fmusic-metadata%2Fget_audio_features.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.freqblog%2Fmusic-metadata%2Fget_audio_features
or MCP find_alternatives. Check mcp-registry/com.freqblog/music-metadata/get_audio_features's live status: https://glimind.com/tool/mcp-registry/com.freqblog/music-metadata/get_audio_features.