Skip to content
hosaka logo

hosaka MCP server

Which MCP servers are hosaka's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to hosaka

Whose server it is
  • Registry namefm.hosaka/ono-sendaiverified in the MCP registry

The registry name sits under hosaka.fm. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools17
  • Server calls itselfono-sendai
  • Server version0.6.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 244 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "check how far along an artist is in their career", the likely first call is resolve_artist.
  • Parameters are untyped or undescribed in 12 of 17 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer243 ms
  • Space in an agent's context≈ 4,768 tokensthe definitions of all its tools (17), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results0 of 17 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 12 of 17

What an agent can do with it

  • can do · check how far along an artist is in their career
  • not sure · see which artists have shared bills with a given artist
  • not sure · find emerging artists related to the music in your Last.fm library

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-30
  • 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`…

  • 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…

  • 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…

  • 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…

  • 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`…

  • 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)…

  • 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…

  • 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`…

  • 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…

  • 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 |…

  • 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…

  • 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…

  • 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…

  • 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 |…

  • 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…

  • 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…

  • 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`…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.hosaka.fm/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.