mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm / alternatives

Live alternatives to mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm

The best live alternatives to mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm right now are mcp-registry/io.github.pipeworx-io/spotify/get_audio_features, mcp-registry/io.github.pipeworx-io/last-fm/track_search, mcp-registry/io.github.pipeworx-io/spotify/get_track, mcp-registry/io.github.pipeworx-io/spotify/get_artist_top_tracks, mcp-registry/io.github.pipeworx-io/librivox/tracks — capability-matched and ranked by current reliability. mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/spotify/get_audio_features	io.github.pipeworx-io/spotify	live status →
mcp-registry/io.github.pipeworx-io/last-fm/track_search	io.github.pipeworx-io/last-fm	live status →
mcp-registry/io.github.pipeworx-io/spotify/get_track	io.github.pipeworx-io/spotify	live status →
mcp-registry/io.github.pipeworx-io/spotify/get_artist_top_tracks	io.github.pipeworx-io/spotify	live status →
mcp-registry/io.github.pipeworx-io/librivox/tracks	io.github.pipeworx-io/librivox	live status →
mcp-registry/space.studiosphere/pulse/analyze_track	space.studiosphere/pulse	live status →
mcp-registry/io.github.pipeworx-io/spotify/search	io.github.pipeworx-io/spotify	live status →
mcp-registry/io.github.pipeworx-io/last-fm/user_top_tracks	io.github.pipeworx-io/last-fm	live status →
mcp-registry/io.github.pipeworx-io/deezer/artist_top	io.github.pipeworx-io/deezer	live status →
mcp-registry/io.apis/apis-io/find_ratings	io.apis/apis-io	live status →
mcp-registry/io.github.pipeworx-io/deezer/track	io.github.pipeworx-io/deezer	live status →
mcp-registry/io.github.pipeworx-io/openverse/audio_related	io.github.pipeworx-io/openverse	live status →

FAQ

What is the best alternative to mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm?

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/last-fm/track_search, mcp-registry/io.github.pipeworx-io/spotify/get_track, mcp-registry/io.github.pipeworx-io/spotify/get_artist_top_tracks, mcp-registry/io.github.pipeworx-io/librivox/tracks. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm down right now?

mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.freqblog%2Fmusic-metadata%2Ffind_tracks_by_bpm.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.freqblog%2Fmusic-metadata%2Ffind_tracks_by_bpm or MCP find_alternatives. Check mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm's live status: https://glimind.com/tool/mcp-registry/com.freqblog/music-metadata/find_tracks_by_bpm.