MCP servers › fm.hosaka › ono-sendai

MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30

ono-sendai MCP server

Registry name fm.hosaka/ono-sendai

hosaka music data — the publisher's title

by hosaka.fm · domain (the registry's namespace rule)Website ↗

Verified music facts for agents: artists, releases, tracks, gigs, similar artists, discovery lists. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-30version 0.6.0streamable HTTP17 tools

Summary

fm.hosaka/ono-sendai is a remote MCP server listed in the official MCP registry at version 0.6.0, under the namespace of the domain hosaka.fm. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 17 tools, 6 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 17
Last tested: 2026-10-30

Tool list size

8,688 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (17 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-30 (mcp.hosaka.fm), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.6.0).

Add to your client

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-30
Mode: read-only (no tool calls)
Latest version: 0.6.0, published 2026-10-30 (registry, as of the 2026-10-30 snapshot)
First listed version: 2026-10-30 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-30
Package and repository: checked 2026-10-30
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 0.6.0 (published 2026-10-30).

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.

What it is

What does this server offer?

Observed inventory

17tools

6resources

0prompts

None of its 17 tools are described as changing anything. For 17 the reading was uncertain, so no mark is shown.

resolve_artiston 1 other server
“Map a name, URL or id to hosaka's verified artist identity (`cluster_id`) with an ambiguity verdict.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
8 inputs
- qstring“Artist name exactly as the user said it”
- urlstring“Discogs, MusicBrainz, Bandcamp, SoundCloud, Spotify, YouTube or official site URL”
- cluster_idstring“64-hex hosaka cluster id”
- discogs_idstring or integer“Discogs artist id (digits)”
- mbidstring“MusicBrainz artist id”
- isrcstring
- artiststring
- trackstring
get_artiston 19 other servers
“Artist card plus any published facet on request.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- keystringrequired“cluster_id (64-hex) or crate slug”
- viewstring
- includearray
- facetsarray“opt-in facets (linked; ≤ 12 or ["all"]): across_the_web, airplay_breadth, arrival, artwork, aura, authorship, bandcamp_emergence, bandcamp_releases, bandcamp_t…”
find_similar_artistson 1 other server
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- keystringrequired
- limitinteger“1–25 (default 10); above 25 the tool answers range_too_large”
get_labelon 4 other servers
“Record-label card (identity, allowlisted facets) with hosaka's over-merge signal when one label page may cover several labels.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- keystringrequired
search_catalogon 109 other servers
“Search releases (masters) by text and facets, with cursor pagination.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
16 inputs
- qstring
- genrestring or array
- stylestring or array
- formatstring or array
- countrystring or array
- labelstring or array
- genre_modestring
- style_modestring
- format_modestring
- country_modestring
- label_modestring
- year_frominteger
- year_tointeger
- cursorstring
- limitinteger“1–100 (default 10); above 100 the tool answers range_too_large”
- includearray“["facet_counts"]: catalogue counts per genre / style / country / decade (+1 unit)”
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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs
- titlestring
- artiststring
- trackstring
- fuzzyboolean
- limitinteger“1–25 (default 10); above 25 the tool answers range_too_large”
- tracksarray“batch: {title, artist?, year?} entries in one call (1 unit), up to the published cap find_tracks_batch_max in hosaka://capabilities (default 25); exclusive wit…”
get_upcoming_gigs
“Upcoming gigs for one artist, or in one city within a date window.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- keystring
- citystring
- fromstring
- tostring
get_profileon 140 other servers
“The linked account's stable, opaque profile id (and display name if set); never ask the user for it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
get_usageon 106 other servers
“The linked account's current-period usage against its temporary allowance, with the 80 % warning and reset time.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- periodstring
list_breakouts
“Artists breaking out or rising per hosaka, with the corroboration observed (press, or bookings ahead of press).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs
- limitinteger“1–50 (default 8); above 50 the tool answers range_too_large”
- tierstring
- corroborationstring
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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- limitinteger“1–50 (default 8); above 50 the tool answers range_too_large”
get_aura
“Aura: signal dimensions converging on an artist within 18 months, with measured 12-month break odds.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- cluster_idstring
- limitinteger“1–50 (default 20); above 50 the tool answers range_too_large”

Show 5 more tools

browse_artists
“Browse hosaka's artist grid by Discogs genre and style, emergence tier and sort.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs
- genrestring“Discogs genre name, e.g.”
- stylestring“Discogs style name, e.g.”
- tierstring“emergence tier”
- sortstring
- limitinteger“1–30 (default 10); above 30 the tool answers range_too_large”
- cursorstring“`pagination.next_cursor` from the previous page”
list_tastemakers
“A section of hosaka's tastemaker index: ones_to_watch is served; leaderboard and early_spinners are withheld until crate classifies them.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- sectionstring“ones_to_watch (classified — the default) | leaderboard | early_spinners (unclassified upstream: present:false until crate publishes a manifest class)”
- limitinteger“1–50 (default 12 — sized to the default token budget with the display-only names listed; above 50 the tool answers range_too_large”
get_festivalon 2 other servers
“A festival card: header facts, identity and lineup as crate publishes them, acts linked to artist cards where a cluster_id exists.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- keystringrequired“festival slug (crate's canonical key); crate publishes no festival index yet — pass the key the user gives you”
get_releaseon 12 other servers
“One release under an artist: a Discogs master (header, sections, artwork links, freshness) or a Bandcamp release (facts, track list).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- keystringrequired“artist cluster_id (preferred) or crate slug”
- master_idstring
- bandcamp_itemstring
- includearray“Bandcamp only: add the track list (≤ 25 tracks with durations and https track links, titles display-only) — a heavy shape; the default card carries tracks_total”
read_surfaceon 1 other server
“hosaka's cluster-keyed surface registry (signal tables behind the facets) and one surface's rows for one cluster.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- namestring“omit for the listing; a registry name for rows”
- clusterstring“with `name`: the 64-hex cluster_id the surface is keyed by (see the registry row's keyspace)”
- limitinteger“rows per page (default: the surface's default_limit; max: its max_limit; the listing pages at 15)”
- cursorstring“`pagination.next_cursor` from the previous page”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 45% of 65
Tools with a description: 100% of 17
Typical description length: 519 characters

The tool set

Counted from the listing

Tools: 17
Size of the list: about 5,781 tokens for an agent to load (characters ÷ 4)
Naming: 17 of 17 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 17 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-30 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.hosaka.fm/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"ono-sendai","type":"http","url":"https://mcp.hosaka.fm/mcp"}'

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "ono-sendai": {
      "type": "streamableHttp",
      "url": "https://mcp.hosaka.fm/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

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

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.ono-sendai]
url = "https://mcp.hosaka.fm/mcp"

Zed · Zed settings file (command: zed: open settings file)

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.hosaka.fm/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.hosaka.fm/mcp	Session opened	matches	our test · 2026-10-30
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-30

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about fm.hosaka/ono-sendai

Answered from the data above

Who publishes fm.hosaka/ono-sendai?

The registry ties the namespace fm.hosaka to the domain hosaka.fm; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does fm.hosaka/ono-sendai need an API key or sign-in?

It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.

Has fm.hosaka/ono-sendai been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-30

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,850 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 17 tools, 6 resources, 0 prompts.
9,449 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-10-30; not classified yet

Pricing modelAI-classified

pending: added in a later update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-30

MCP capability

resources, tools

our test · 2026-10-30

Transport

streamable HTTP

registry · 2026-10-30

Required credentials

none declared

registry · 2026-10-30 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-30

Lifecycle status

active

registry · 2026-10-30

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “fm.hosaka/ono-sendai: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/fm.hosaka/ono-sendai

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/fm.hosaka/ono-sendai)](https://protocolprobe.com/mcp/servers/fm.hosaka/ono-sendai)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology