FreqBlog Music Metadata MCP server
com.freqblog/music-metadatafreqblog.comstreamable-httpv1.1.0Scanned
Audio features + harmonic set-building for tracks by name/ISRC. Spotify audio-features replacement.
15 tools: 3 change things and 12 only read.
- Reads private data · 0
- Reads text others write · 14
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FreqBlog Music Metadata MCP server can do
The FreqBlog Music Metadata MCP server is published by freqblog.com, a domain the MCP Registry verified. It has 15 tools. It can create or change data (3 tools: score_transition, suggest_next_track and build_setlist), but cannot delete data. 12 tools only read.
14 tools bring in text other people can write (get_audio_features, get_audio_features_batch, search_catalog and 11 more).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 3Claude Code: ask
build_setlistOrder a crate of 2-100 catalog tracks into a beat-matched DJ set that follows an energy arc, keeping each consecutive transition harmonically and tempo-smooth.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Order a crate of 2-100 catalog tracks into a beat-matched DJ set that follows an energy arc, keeping each consecutive transition harmonically and tempo-smooth. `arc` is one of peak_time (default — builds to a peak then eases), warmup, cooldown, or flat. Returns the `arc`, `count`, an overall `flow_score` (0-100), the `tracks` in play order, the per-step `transitions` ({from_index, to_index, score, reason}), and `omitted` (ids not found in the catalog, or with no audio features on file yet). Feed tracks[].itunes_track_id into a Rekordbox/Serato export to drop the set straight into your DJ software. track_ids are catalog itunes_track_ids. Costs 5 quota units.
Annotations the server declares
- title: Build Setlist
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
score_transitionScore how well one catalog track mixes into another (0-100) — the pairwise DJ transition score no raw key/BPM API gives you.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Score how well one catalog track mixes into another (0-100) — the pairwise DJ transition score no raw key/BPM API gives you. Combines Camelot-wheel key compatibility, octave-aware BPM proximity (half/double-time counts as a match), and energy smoothness. Returns the overall `score`, per-component scores (`harmonic`/`tempo`/`energy`), a `detail` block (key_relation, both Camelot keys, both BPMs, bpm_delta, bpm_octave_matched, both energies, energy_delta), and a one-line human `reason` (e.g. "8A->9A adjacent (+1), 126->128 BPM (+2), energy +0.04 — clean uplifting mix"). Both ids are catalog itunes_track_ids — get them from search_catalog or the itunes_track_id field of a get_audio_features result. Costs 1 quota unit.
Annotations the server declares
- title: Score Transition
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
suggest_next_trackGiven a seed track, return the top-N catalog tracks to play NEXT, ranked by transition score.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Given a seed track, return the top-N catalog tracks to play NEXT, ranked by transition score. Each suggestion carries the same `score`, per-component scores and human `reason` as score_transition (e.g. "11B->11B same key, 118->117 BPM (-0.29), energy +0.12"), plus its `genre` and `genre_relation` to the seed. GENRE-AWARE by default (cross_genre=auto): off-genre picks that only coincidentally share the seed's key/BPM sink to the bottom — use cross_genre=strict for same-genre-family only, or allow for the old harmonic-only ranking. It is the seed's sonic neighbours re-ranked for a clean mix. Returns `seed`, `count`, and a `suggestions` array of {track, score, components, reason}. seed_track_id is a catalog itunes_track_id from search_catalog or a get_audio_features result. Pair with build_setlist to order a whole crate. Costs 3 quota units.
Annotations the server declares
- title: Suggest Next Track
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 12Show 12 read-only tools
discover_tracksFind catalog tracks by criteria, with no seed track: tempo, key, genre, release year, chart placement and audio-feature ranges in one call — e.g.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find catalog tracks by criteria, with no seed track: tempo, key, genre, release year, chart placement and audio-feature ranges in one call — e.g. house at 122-126 BPM in 8A or its neighbours with energy above 0.7: min={"tempo": 122, "energy": 0.7}, max={"tempo": 126}, key="8A", harmonic=true, genre="house". At least one narrowing filter is required (a tempo/feature bound, key, mode, genre, year or chart). Returns `results` (one per recording, each with its bpm, camelot, energy, danceability, valence, acousticness and loudness_db plus catalog metadata), `total_matches` (exact up to 1,000; `total_matches_capped` above that), `next_offset` for the next page, and `filters` — what was applied and how many tracks each filter removed (`dropped_by`); if the list is short, loosen the largest one. energy, danceability and valence are on FreqBlog's own scales, so derive thresholds from values you have seen rather than from another service's. Results reach a depth of 500 per query; narrow the filters to go further. Pass a result's itunes_track_id to get_audio_features for every field, or to suggest_next_track / build_setlist. Costs 1 quota unit.
Annotations the server declares
- title: Discover Tracks by Criteria
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
find_compatible_keysGiven a Camelot key (e.g.No findings
Why it is in this group
- The name "find_compatible_keys" says "find": a word for reading.
Description, as the server wrote it Given a Camelot key (e.g. "8A", "12B"), return the harmonically compatible keys for DJ mixing — the same key, the relative major/minor, and the adjacent +/-1 keys on the Camelot wheel. With `extended=true` also returns the +7/-7 energy-boost / energy-drop keys. Pure music theory — no catalog lookup and no quota cost. Pair with find_tracks_by_key to then pull actual tracks in each compatible key.
Annotations the server declares
- title: Find Harmonically Compatible Keys
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
find_similar_tracksTracks that SOUND like one seed track or a set of up to 10, optionally restricted by tempo, key, genre, year, chart or audio-feature ranges — e.g.Reads text others writeNo findings
Why it is in this group
- The name "find_similar_tracks" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Tracks that SOUND like one seed track or a set of up to 10, optionally restricted by tempo, key, genre, year, chart or audio-feature ranges — e.g. "like these three, but 120-128 BPM in 8A or its neighbours": seed_tracks=[...], min={"tempo": 120}, max={"tempo": 128}, key="8A", harmonic=true. Ranked mainly on a PANNs audio embedding (how the recording sounds) blended with an audio-feature similarity. Results are one per recording, with `score`, `genre_relation` to the seed and, with several seeds, `matched_seed`. With filters, results are the closest-sounding tracks that pass every filter, and `filters` reports what was applied and how many catalog tracks each one removed (`dropped_by`) — loosen the largest if the list is short. Use get_recommendations instead when you want preferred target values (target energy etc.) rather than hard filters. Costs 1 quota unit. PANNs (Kong et al., 2020) is used under CC BY 4.0.
Annotations the server declares
- title: Find Similar-Sounding Tracks
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
find_tracks_by_bpmFind catalog tracks near a target tempo.Reads text others writeNo findings
Why it is in this group
- The name "find_tracks_by_bpm" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find catalog tracks near a target tempo. Returns tracks whose BPM is within +/-`tolerance` of `bpm`, ordered by closeness then by an internal catalogue ordering key (not an audience metric) — useful for DJ set planning, workout playlists, or tempo-matching. Each returned track carries full audio features. To also constrain by musical key, combine with find_tracks_by_key.
Annotations the server declares
- title: Find Tracks by BPM
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
find_tracks_by_keyFind catalog tracks in a given musical key — for harmonic mixing and key-locked playlists.Reads text others writeNo findings
Why it is in this group
- The name "find_tracks_by_key" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find catalog tracks in a given musical key — for harmonic mixing and key-locked playlists. `key` accepts Camelot ("8A"), Open Key ("1m"), or a key name ("A-Minor", "F#-Major"). Returns tracks ordered by an internal catalogue ordering key (not an audience metric), each with full audio features. To discover which keys mix well with a given key first, use find_compatible_keys.
Annotations the server declares
- title: Find Tracks by Musical Key
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_audio_featuresGet audio features for ONE track — BPM, musical key (name + Camelot + Open Key), energy, danceability, valence, acousticness, loudness, mood, mood_vector, genre, time signature, du…Reads text others write1 finding
Why it is in this group
- The name "get_audio_features" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,757 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...uzzy or partial name, call search_catalog first to find the exact track."
Description, as the server wrote it Get audio features for ONE track — BPM, musical key (name + Camelot + Open Key), energy, danceability, valence, acousticness, loudness, mood, mood_vector, genre, time signature, duration and more. `preview_loudness.integrated_lufs` is the BS.1770 integrated loudness (LUFS) of the 30-second preview — often the chorus, so typically a little louder than the full track. Fields follow the layout of Spotify's retired /audio-features endpoint. Provide AT LEAST ONE identifier — if you know several, send them all rather than choosing; they resolve by precedence (`track` > `isrc` > `mbid` > `spotify_id`) and the rest are ignored: - `track` (optionally with `artist`) — e.g. track="Blinding Lights", artist="The Weeknd". - `isrc` — e.g. "USUM71900001". - `mbid` — a MusicBrainz recording UUID. - `spotify_id` — a Spotify track ID, URI, or URL (resolved per request by reading the track's title from Spotify's public embed page and matching it against our catalogue — no Spotify IDs are stored; ambiguous titles miss rather than guess — prefer `track`/`isrc` for full coverage). Returns a JSON object of features. Some feature fields may be null for tracks resolved via the fallback catalogs (only audio-derived values are present for fully analysed tracks). VALUES are FreqBlog's own analysis, NOT on Spotify's scale: energy and valence are models of how energetic / positive the preview sounds, both on our own scales (derive thresholds from our values, don't copy Spotify-tuned ones); danceability and acousticness are on AcousticBrainz's scale -- its classifier where available, else a model that listens to the preview, built on PANNs embeddings (Kong et al. 2020, CC BY 4.0); instrumentalness is a vocal-detection model's score for the 30-second preview (not the whole track); speechiness and liveness are currently null for catalogue tracks; time_signature is ASSUMED 4 (4/4) on every track, not measured. KEY: treat `key` as a best guess when `key_confidence` < 0.8 (measured against musicians' annotations: at >= 0.9 it is exact 77% / Camelot-compatible 88%). If a track name is not yet in the catalog, the API holds the request during the on-demand ingest and usually returns the fully analysed track inline in this same call; only if the ingest runs long does it fall back to a queued response you can re-poll shortly (~15s). If the track turns out not to be on any streaming source we can analyse, you get a definitive not-found instead — that verdict is terminal for ~7 days, so don't retry it. If you only have a fuzzy or partial name, call search_catalog first to find the exact track.
Annotations the server declares
- title: Get Audio Features
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_audio_features_batchGet audio features for MANY tracks in one call (up to 50 processed) — ideal for analysing a whole playlist at once.Reads text others writeNo findings
Why it is in this group
- The name "get_audio_features_batch" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get audio features for MANY tracks in one call (up to 50 processed) — ideal for analysing a whole playlist at once. Identify each item by name (`track`/`artist`), by `isrc` (matched exactly first — best for CJK / K-pop / niche tracks whose fuzzy name-match misses), or both (ISRC first, name as the fallback). One bad entry never fails the batch. Items beyond the 50-per-call cap come back with `found: false` and `backfill_status: "over_limit"`; an item missing BOTH `track` and `isrc` comes back `"invalid_no_query"`. Neither is processed or charged — the response's `skipped` field counts them, so split a long list into calls of <=50 and resubmit any skipped rows. Returns counts (`found` / `not_found` / `skipped`) plus a per-track `results` array, where each entry's `result` is the same feature object as get_audio_features (or null when not found), and `isrc` is echoed back. An item is billed only when it returns features or queues an on-demand ingest; an ISRC/name with no match anywhere is free. A track you queue and then collect costs ONE unit, not two — the call that collects it is free. For a `found: false` item, `backfill_status` `queued` / `processing` / `deferred` means retry later; `unavailable` is terminal (carries `terminal`, `reason`, `retry_after_days` — treat it as a miss until then); null means no match anywhere. For a single track, use get_audio_features.
Annotations the server declares
- title: Get Audio Features (Batch)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_recommendationsRecommended tracks for one or more seed tracks, in the shape of Spotify's retired GET /v1/recommendations.Reads text others write1 finding
Why it is in this group
- The name "get_recommendations" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 3,193 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t, read that BEFORE assuming the catalogue is thin. Costs 2 quota units."
Description, as the server wrote it Recommended tracks for one or more seed tracks, in the shape of Spotify's retired GET /v1/recommendations. Takes up to 5 catalog seed tracks and returns catalogue tracks that sound like the set as a whole — ranked on the same similarity as find_similar_tracks (mainly a PANNs audio embedding, blended with audio features), RE-RANKED by genre affinity (so a close-sounding cross-genre track doesn't outrank same-genre picks). Returns `seeds` (each {id, found}), `count`, and `tracks` (each {track, score, genre_relation}; each track carries its `genre`). `genre_relation` is "same", "compatible" (different but mixable family), "cross" (unrelated), or "unknown" (either side has no mapped genre), measured against the PRIMARY seed — the first of your seed_tracks we could actually use, so reordering seed_tracks changes it and a skipped seed never becomes the reference. With a SINGLE seed the field is the ranking's own verdict, so it explains the order (same as suggest_next_track). With SEVERAL seeds the ranking considers ALL of them while the label stays relative to your primary seed, so a "cross" label on a multi-seed call does NOT mean the track was pushed down — it may share a family with another of your seeds. `score` is the similarity to the seed set (the same blended similarity find_similar_tracks returns); genre affinity and target_ preferences influence the ORDER, not the score, so the list is NOT strictly score-descending. Use cross_genre=strict to return same-genre-family tracks ONLY (off-genre dropped server-side), or allow to disable the genre ranking. seed_tracks are catalog itunes_track_ids from search_catalog or the itunes_track_id field of a get_audio_features result. NO id? Pass `track` (+ optional `artist`) instead and we resolve the name to the best catalog match and seed on it — the resolved track is echoed back as `seed_query`; seed_tracks wins if both are given. TUNING: `min`/`max` are HARD filters and `target` is a preference (nearer ranks higher, nothing removed), over acousticness, danceability, duration_ms, energy, loudness, tempo and valence. NOTE: `popularity` (2026-08-27), `liveness`, `speechiness` (2026-09-26) and `instrumentalness` (2026-09-27) are RETIRED as tunables and return a 400 — popularity recorded how a track entered our catalogue, not audience size; the other three are returned as null for catalogue tracks. Values are FreqBlog's own (not Spotify's): energy and valence (models of how energetic / positive the preview sounds) on our own scales, danceability/acousticness on AcousticBrainz's scale — derive thresholds from our values rather than reusing Spotify-tuned ones. e.g. min={"tempo": 100}, max={"tempo": 130}, target={"energy": 0.8} for energetic 100-130 BPM tracks. When you tune, the response adds a `filters` block saying what applied, how many tracks each bound removed (`dropped_by`) and whether the bounds ran out of catalogue before `limit` (`limit_reached`) — if the list comes back short, read that BEFORE assuming the catalogue is thin. Costs 2 quota units.
Annotations the server declares
- title: Get Recommendations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_by_descriptionFind catalog tracks from a plain-language description of how they sound — e.g.Reads text others writeNo findings
Why it is in this group
- The name "search_by_description" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find catalog tracks from a plain-language description of how they sound — e.g. "melancholic piano, slow", "dark ambient strings", "upbeat acoustic guitar, fast". Understands instruments and voice (piano, guitar, acoustic guitar, violin, cello, strings, harp, flute, sax, brass, organ, choir, a cappella, rap, 808/drum machine, orchestral), mood (sad/melancholic, dark/eerie, angry, ambient, happy/upbeat, chill/relaxed), character (acoustic, instrumental, with vocals, energetic, soft, danceable), tempo (slow <= 95 BPM, mid-tempo, fast >= 125 BPM, applied as filters) and any catalog genre. Sound words are scored from audio analysis of each track, not titles; every word has to hold. The response's `description.understood` shows how each word was read and `ignored_words` lists words that were NOT used — rephrase those. Each result has `match` (0-1) and a per-word `matched` breakdown. Costs 1 quota unit.
Annotations the server declares
- title: Search Tracks by Description
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_catalogFull-text search the catalog by any mix of track / artist / album tokens.Reads text others writeNo findings
Why it is in this group
- The name "search_catalog" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Full-text search the catalog by any mix of track / artist / album tokens. Use this to resolve a fuzzy, partial, or misspelled name into concrete tracks BEFORE calling get_audio_features. Each hit carries `chart_peak`: the best chart position we hold, 1-100 with 100 = a number-one. `null` means no placement we hold — treat that as UNKNOWN, not unpopular, and note it is NOT an audience-size figure. Placements come from the Apple Music and Deezer charts we track (since Aug 2026) and Billboard year-end charts (1960-2025). Returns lightweight stubs (itunes_track_id, track_name, artist_name, album, etc.) ranked by relevance — NOT audio features. Take the best match's track_name + artist_name and pass them to get_audio_features, or reuse its itunes_track_id as a `track_id` seed for discovery tools. ⚠ Each hit carries a `seedable` boolean. Only a hit with `seedable: true` can be used as a seed for get_recommendations / suggest_next_track / build_setlist / score_transition — those work off the similarity index, which holds only tracks we have analysed, and about a quarter of the catalogue is not analysed yet. **Prefer the highest-ranked hit with `seedable: true`.** Seeding with a `seedable: false` id returns a 404; if that track is the one you want, call get_audio_features on it first to queue analysis, then retry.
Annotations the server declares
- title: Search Music Catalog
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
tag_trackGet a compact, clearly labelled tag list for a track — energy / danceability / valence / acousticness / instrumentalness (instrumental vs vocal, judged on the 30-second preview), p…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get a compact, clearly labelled tag list for a track — energy / danceability / valence / acousticness / instrumentalness (instrumental vs vocal, judged on the 30-second preview), plus a mood tag and a broad genre tag. It is a tag-shaped projection of the same open-data analysis get_audio_features returns (no audio upload, no extra compute), so it costs the same 1 quota unit, charged only on a served result. EVERY tag carries its own `confidence` and `provenance`: - confidence: measured (a numeric audio feature, source in provenance) | derived (MIREX mood from valence+energy) | model-estimated (AcousticBrainz mood SVM probability — research-grade, raw prob in `value`) | catalog-genre (broad catalogue tag, not fine-grained). - provenance: librosa | panns | valence+energy | acousticbrainz | catalog. `value` is the [0,1] score for numeric tags and null for label-only tags (mood category, genre). Provide AT LEAST ONE identifier: `track` (optionally with `artist`), `isrc`, `mbid`, `spotify_id`, or `track_id` (catalog itunes_track_id). If you know several, send them all — they resolve by precedence (`track` > `isrc` > `track_id` > `mbid` > `spotify_id`) and the rest are ignored, so you never have to pick. The broad, reliable coverage is the MEASURED tags from our own analysis (librosa + a PANNs-based model) over the analysed catalogue (plus on-demand by name); MBID/ISRC additionally reach 7.5M+ AcousticBrainz recordings WHEN you supply that identifier. Returns { track, count, tags:[{tag, category, value, confidence, provenance}], disclaimer }. For the full numeric feature set use get_audio_features; for nearest tracks use a discovery tool.
Annotations the server declares
- title: Tag Track
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write14
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.freqblog.com/mcp: tools/list returned 15 tools to an anonymous client, including score_transition (write), suggest_next_track (write), build_setlist (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 2,757 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...uzzy or partial name, call search_catalog first to find the exact track."
The description is 3,193 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t, read that BEFORE assuming the catalogue is thin. Costs 2 quota units."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 added, 12 changed.+3 added~12 changedView diff
- Added:discover_tracksOnly reads
- Added:find_similar_tracksOnly reads
- Added:search_by_descriptionOnly reads
- Changed:build_setlistChanges thingsannotations
- Changed:find_compatible_keysOnly readsannotations
- Changed:find_tracks_by_bpmOnly readsannotations
- Changed:find_tracks_by_keyOnly readsannotations
- Changed:get_audio_featuresOnly readsdescriptionannotations
- Changed:get_audio_features_batchOnly readsannotations
- Changed:get_recommendationsOnly readsdescriptionannotations
- Changed:get_related_artistsOnly readsdescriptionannotations
- Changed:score_transitionChanges thingsannotations
- Changed:search_catalogOnly readsannotations
- Changed:suggest_next_trackChanges thingsannotations
- Changed:tag_trackOnly readsdescriptionannotations
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http music-metadata https://mcp.freqblog.com/mcpclaude mcp add --transport http music-metadata https://mcp.freqblog.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__music-metadata__get_audio_features",
"mcp__music-metadata__get_audio_features_batch",
"mcp__music-metadata__search_catalog",
"mcp__music-metadata__find_tracks_by_bpm",
"mcp__music-metadata__find_tracks_by_key",
"mcp__music-metadata__discover_tracks",
"mcp__music-metadata__find_similar_tracks",
"mcp__music-metadata__search_by_description",
"mcp__music-metadata__find_compatible_keys",
"mcp__music-metadata__get_recommendations",
"mcp__music-metadata__get_related_artists",
"mcp__music-metadata__tag_track"
],
"ask": [
"mcp__music-metadata__score_transition",
"mcp__music-metadata__suggest_next_track",
"mcp__music-metadata__build_setlist"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as music-metadata. Review it before you use it.
Capability tags behind 14 rules
- mcp__music-metadata__get_audio_features untrusted-input
- mcp__music-metadata__get_audio_features_batch untrusted-input
- mcp__music-metadata__search_catalog untrusted-input
- mcp__music-metadata__find_tracks_by_bpm untrusted-input
- mcp__music-metadata__find_tracks_by_key untrusted-input
- mcp__music-metadata__discover_tracks untrusted-input
- mcp__music-metadata__find_similar_tracks untrusted-input
- mcp__music-metadata__search_by_description untrusted-input
- mcp__music-metadata__score_transition untrusted-input
- mcp__music-metadata__suggest_next_track untrusted-input
- mcp__music-metadata__build_setlist untrusted-input
- mcp__music-metadata__get_recommendations untrusted-input
- mcp__music-metadata__get_related_artists untrusted-input
- mcp__music-metadata__tag_track untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.freqblog/music-metadata/verify?hash=d61948ab8e57b68ed810440ed36d22f7278389d2372a6e32f24ef15c733c71b2" | jq -e '.changed == false'Pinned hash d61948ab8e57, from Nov 13, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.freqblog/music-metadata/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.freqblog/music-metadata)Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.
FreqBlog Music Metadata MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FreqBlog Music Metadata MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FreqBlog Music Metadata MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FreqBlog Music Metadata MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FreqBlog Music Metadata MCP server have?
- 15 tools: 3 write, 12 read. score_transition, suggest_next_track, build_setlist, get_audio_features, get_audio_features_batch, search_catalog, find_tracks_by_bpm, find_tracks_by_key and 7 more.
Does the FreqBlog Music Metadata MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FreqBlog Music Metadata MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FreqBlog Music Metadata MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.