FreqBlog Music Metadata
Audio features (BPM, key, mood, genre) for real tracks - a Spotify audio-features replacement.
https://mcp.freqblog.com/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- freqblog-music
- Version
- 1.27.2
- Capability keys
- experimental, prompts, resources, tools
- Tool names
- get_audio_features, get_audio_features_batch, search_catalog, find_tracks_by_bpm, find_tracks_by_key, find_compatible_keys, score_transition, suggest_next_track, build_setlist, get_recommendations, get_related_artists, tag_track
FreqBlog music audio-features tools. Look up BPM, musical key (name + Camelot + Open Key), energy, danceability, valence, acousticness, instrumentalness, mood, genre and 30+ more for real tracks — a drop-in replacement for Spotify's removed audio-features endpoint. No audio upload needed; identify a track by name (+artist), ISRC, MusicBrainz ID, or Spotify ID. Typical flow: use search_catalog to resolve a fuzzy or partial name into a concrete track, then get_audio_features for one track (or get_audio_features_batch for a whole playlist). Use find_tracks_by_bpm / find_tracks_by_key to discover tracks by tempo or key, and find_compatible_keys for harmonic-mixing (Camelot wheel) suggestions. Set flow (the differentiator): score_transition rates how well one track mixes into another (0-100); suggest_next_track ranks the best next picks for a seed; build_setlist orders a whole crate into a beat-matched energy arc. These take catalog itunes_track_ids (from search_catalog, or the itunes_t
Reported Aug 17, 2026, 05:03 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 725ms
- respondsMCP initialize · 8s limit · HTTP 200 · 1,168ms
- respondsMCP initialize · 8s limit · HTTP 200 · 682ms
- respondsMCP initialize · 8s limit · HTTP 200 · 955ms