ENFRESDE
List your agent

hosaka music data

MCP server · hosted · v0.6.0 · fm.hosaka/ono-sendai
Online · tested 2h agoNEW · 3h agoSeen in the registry 2h ago

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

Website ↗How to connect ↓

What it does

hosaka music data is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.6.0
PriceNot in the registry
First seen30 Oct 2026
Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://mcp.hosaka.fm/mcp streamable-http

In Claude Code: claude mcp add --transport http hosaka-music-data https://mcp.hosaka.fm/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "hosaka-music-data": {
      "url": "https://mcp.hosaka.fm/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE hosaka music data answered an MCP connection on 30 Oct 2026 and introduced itself as ono-sendai 0.6.0 (MCP protocol 2025-06-18).

17 tools offered to AI assistants

  • resolve_artist · Map 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`, `cluster_id`, `discogs_id`
  • get_artist · Artist 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"] (linked, +1 unit each; 1
  • find_similar_artists · Artists 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 verified artist. Inputs:
  • get_label · Record-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`: label cluster_id (64-hex
  • search_catalog · Search 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`, `year_from`, `yea
  • find_tracks · Find 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: [...]` (≤ 25); `limit
  • get_upcoming_gigs · Upcoming 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` YYYY-MM-DD. Returns
  • get_profile · The 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.name`, `data.account_m
  • get_usage · The 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 "current" in v1. Returns:
  • list_breakouts · Artists 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; `corroboration`: corroborated | b
  • list_ones_to_watch · The 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). Returns: `data.item
  • get_aura · Aura: 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 20). Returns: `data.
Show 5 more
  • browse_artists · Browse 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 | rising | steady; `so
  • list_tastemakers · A 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 | leaderboard | ear
  • get_festival · A 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 festival index — as
  • get_release · One 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 cluster_id from reso
  • read_surface · hosaka'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; `name` + `cluster` (6

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.hosaka.fm/mcpDECLAREDSRC-001 Official MCP Registry2h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2h ago
Websitehttps://hosaka.fm/agentsDECLAREDSRC-001 Official MCP Registry2h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2h ago
Version0.6.0DECLAREDSRC-001 Official MCP Registry2h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2h ago

Change history

  • NEW30 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run hosaka music data? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor hosaka music dataLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of hosaka music data?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedInListed on Electra Index
<a href="https://electraindex.com/mcp/hosaka-music-data?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/hosaka-music-data" alt="Listed on Electra Index"></a>

Questions about hosaka music data

How do I connect hosaka music data?

Use the hosted endpoint https://mcp.hosaka.fm/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does hosaka music data offer?

When Electra Index connected on 30 Oct 2026, it listed 17 tools: resolve_artist, get_artist, find_similar_artists, get_label, search_catalog, find_tracks, get_upcoming_gigs, get_profile and more. The full list is in "Live check" above.

Is hosaka music data online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.