hosaka music data

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 设计、图片与音频

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://mcp.hosaka.fm/mcp

claude mcp add --transport http ono-sendai https://mcp.hosaka.fm/mcp

{
  "mcpServers": {
    "ono-sendai": {
      "url": "https://mcp.hosaka.fm/mcp"
    }
  }
}

{
  "servers": {
    "ono-sendai": {
      "type": "http",
      "url": "https://mcp.hosaka.fm/mcp"
    }
  }
}

https://mcp.hosaka.fm/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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`, `mbid`. Returns: `cluster_id`, `displa

• 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; 10 rows, 5 each when `view: full` carries

• 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: `key`: cluster_id from resolve_artist,

• 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) or crate slug. Returns: label facets;

• 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`, `year_to`; `limit` 1–100 (default 10); `curs

• 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` 1–25 (default 10). Returns: `data.resu

• 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: `data.gigs[]` {date, time, name, event

• 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_mode`, `data.linked_since`. Auth: linked.

• 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: `allowance`, `used`, `warning_80`, `rese

• 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 | booking_ahead. Returns: `data.items[]` {c

• 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.items[]` {rank, name, slug, emergenceTier, m

• 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.items[]` or `data.aura` {cluster_id, art

• 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; `sort`: discovery | reach; `limit` 1–30; `c

• 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 | early_spinners; `limit` 1–50 (default 12).

• 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 — ask for the key). Returns: `display`, `slu

• 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 resolve_artist, or slug; one of `master_id`

• 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` (64-hex) → rows; `limit`; `cursor`. Return

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（hosaka.fm）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 299 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 17 个工具描述，未发现针对 AI 的隐藏指令

与“设计、图片与音频”中的其他服务器比较i

• 星标数多于此分类中其他 2814 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 2814 个服务器的 77% 更新
• 基础检查结果等于或优于此分类中其他 2814 个服务器的 44%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README