Agents Index

hosaka music data

OnlineNew

Verified music facts for agents: artists, releases, tracks, gigs, similar artists, discovery lists.

Visit publisherConnectJSON

What it can do: 17 tools

  • resolve_artist read-onlyMap a name, URL or id to hosaka's verified artist identity (`cluster_id`) with an ambiguity verdict. Use: the user names an artist; you hold a Discogs / MusicBrainz / Bandcamp URL or id. Inputs: one of `q`, `url`, `clust
  • get_artist read-onlyArtist card plus any published facet on request. Use: an artist's facts, releases or signals. Inputs: `key`: cluster_id from resolve_artist, or slug; `view`: summary | standard | full; `include`: ["similar", "gigs"] (lin
  • find_similar_artists read-onlyArtists adjacent to one artist, with the axes hosaka observed (co-appearance, radio co-play, DJ champions, lineage, credits, label mates) and counts — no composite score. Use: artists like X; a listening path from a veri
  • get_label read-onlyRecord-label card (identity, allowlisted facets) with hosaka's over-merge signal when one label page may cover several labels. Use: the user asks about a label; an artist card names a label to expand. Inputs: `key`: labe
  • search_catalog read-onlySearch releases (masters) by text and facets, with cursor pagination. Use: releases matching a description; candidate names (rows carry artist_cluster_id). Inputs: `q` and/or `genre`, `style`, `format`, `country`, `label
  • find_tracks read-onlyFind tracks by title, resolve artist + track, or a batch of up to 25 tracks in one call — release facts, durations, cluster_id. Use: the user names a song; a tracklist. Inputs: `title` OR `artist` + `track` OR `tracks: [
  • get_upcoming_gigs read-onlyUpcoming gigs for one artist, or in one city within a date window. Use: where or when an artist plays; what is on in a city. Inputs: `key`: cluster_id from resolve_artist or slug, OR `city` (exact spelling); `from`, `to`
  • get_profile read-onlyThe linked account's stable, opaque profile id (and display name if set); never ask the user for it. Use: the host needs a stable user handle; after sign-in to confirm the link. Inputs: none. Returns: `data.id`, `data.na
  • get_usage read-onlyThe linked account's current-period usage against its temporary allowance, with the 80 % warning and reset time. Use: the user asks how much is left; after quota_exceeded or a quota warning. Inputs: `period`: only "curre
  • list_breakouts read-onlyArtists breaking out or rising per hosaka, with the corroboration observed (press, or bookings ahead of press). Use: who is breaking through now. Inputs: `limit` 1–50 (default 8); `tier`: breakout | rising; `corroboratio
  • list_ones_to_watch read-onlyThe ones-to-watch slice of hosaka's tastemaker index: rising names with emergence and momentum tiers from early-moving curators and DJs. Use: up-and-coming artists; a discovery playlist. Inputs: `limit` 1–50 (default 8).
  • get_aura read-onlyAura: signal dimensions converging on an artist within 18 months, with measured 12-month break odds. Use: is an artist about to break. Inputs: `cluster_id` from resolve_artist (omit for the index); `limit` 1–50 (default
  • browse_artists read-onlyBrowse hosaka's artist grid by Discogs genre and style, emergence tier and sort. Use: artists in a genre or style, by emergence tier. Inputs: `genre`, `style`: exact Discogs vocabulary (`Electronic`); `tier`: breakout |
  • list_tastemakers read-onlyA section of hosaka's tastemaker index: ones_to_watch is served; leaderboard and early_spinners are withheld until crate classifies them. Use: up-and-coming artists, or who moves a scene. Inputs: `section`: ones_to_watch
  • get_festival read-onlyA festival card: header facts, identity and lineup as crate publishes them, acts linked to artist cards where a cluster_id exists. Use: a festival whose slug you have. Inputs: `key`: the festival slug (crate publishes no
  • get_release read-onlyOne release under an artist: a Discogs master (header, sections, artwork links, freshness) or a Bandcamp release (facts, track list). Use: a discography row names the release; one specific release. Inputs: `key`: artist
  • read_surface read-onlyhosaka's cluster-keyed surface registry (signal tables behind the facets) and one surface's rows for one cluster. Use: row-level detail behind a facet; which surfaces exist. Inputs: no arguments → the registry listing; `

Connect it

Claude Code
claude mcp add --transport http hosaka-music-data https://mcp.hosaka.fm/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.hosaka.fm/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "hosaka-music-data": {
      "url": "https://mcp.hosaka.fm/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "hosaka-music-data": {
      "type": "http",
      "url": "https://mcp.hosaka.fm/mcp"
    }
  }
}

Questions

What does hosaka music data do?

Verified music facts for agents: artists, releases, tracks, gigs, similar artists, discovery lists. It exposes 17 tools to AI assistants.

What tools does hosaka music data provide?

17 tools, including resolve_artist, get_artist, find_similar_artists, get_label, search_catalog, find_tracks, get_upcoming_gigs, get_profile, get_usage, list_breakouts, list_ones_to_watch, get_aura….

How do I connect hosaka music data to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.hosaka.fm/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does hosaka music data require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is hosaka music data online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes hosaka music data?

hosaka.fm. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Audio, Voice & Music