Yandex Music (unofficial)
PYPI · YANDEX-MUSIC-MCP
Unofficial Yandex Music server: search, likes, history, My Wave, playlists. Token stays local.
Available components
Last scanned (12 hours ago)
Scores higher than 55% of PyPI servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 977 tokens (~51/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +26
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
- 12 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed pypi/yandex-music-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_info ~24
Проверка подключения: логин, имя и статус подписки Плюс.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
add_tracks_to_playlist ~60
Добавляет треки в мой плейлист. track_ids — id из других инструментов ("123:456" или "123").
| Name | Type | Req | Description |
|---|---|---|---|
| at_start | boolean | – | – |
| kind | integer | yes | – |
| track_ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_playlist ~43
Создаёт новый плейлист (по умолчанию приватный). Возвращает его kind.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | – |
| visibility | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_playlist ~73
НЕОБРАТИМО удаляет мой плейлист целиком. Перед вызовом обязательно спроси пользователя. confirm_title — точное название удаляемого плейлиста (защита от удаления не того плейлиста).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_title | string | yes | – |
| kind | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
export_tracks_to_file ~136
Выгружает ВСЕ треки (лайки или плейлист) в текстовые файлы на компьютер, не загружая их в чат: .txt («Исполнитель — Название», по строке) и .csv (с альбомом, годом, жанром, id; для лайков — дата лайка). Файлы кладутся в «Документы/Yandex Music exports» (или в YANDEX_MUSIC_EXPORT_DIR). Для source="playlist" нужен kind.
| Name | Type | Req | Description |
|---|---|---|---|
| file_name | – | – | – |
| kind | – | – | – |
| owner_uid | – | – | – |
| source | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_album_tracks ~29
Информация об альбоме и его треклист.
| Name | Type | Req | Description |
|---|---|---|---|
| album_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_artist_tracks ~32
Популярные треки артиста.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_id | integer | yes | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_chart ~26
Текущий чарт Яндекс Музыки.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_liked_tracks ~62
Треки из «Мне нравится», от последних лайков к старым, с датой лайка (liked_at). Для анализа вкуса бери limit побольше (до 500).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_listening_history ~40
Недавно прослушанные треки (история прослушиваний), сгруппированные по дням.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_my_wave ~50
Порция треков из «Моей волны» — персональных рекомендаций. batches — сколько порций (≈5 треков каждая).
| Name | Type | Req | Description |
|---|---|---|---|
| batches | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_playlist_by_url ~127
Треки по ссылке на Яндекс Музыку — в том числе чужого публичного плейлиста. Понимает ссылки вида music.yandex.ru/users/<логин>/playlists/<номер>, music.yandex.ru/playlists/<uuid> (новый формат, в т.ч. lk.…) и ссылки на альбом /album/<id>. Подходит любой домен Яндекс Музыки (.ru, .com, .by, .kz и т.д.).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_playlist_tracks ~56
Треки плейлиста. По умолчанию — мой плейлист; owner_uid — для чужого публичного.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | integer | yes | – |
| limit | integer | – | – |
| owner_uid | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_similar_tracks ~41
Похожие треки по версии Яндекса (track_id в формате "123" или "123:456").
| Name | Type | Req | Description |
|---|---|---|---|
| track_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
like_tracks ~29
Ставит лайк («Мне нравится») трекам.
| Name | Type | Req | Description |
|---|---|---|---|
| track_ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_my_playlists ~31
Все мои плейлисты (kind — идентификатор плейлиста для других инструментов).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
remove_tracks_from_playlist ~39
Удаляет указанные треки из моего плейлиста.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | integer | yes | – |
| track_ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search ~53
Поиск по каталогу Яндекс Музыки. type сужает поиск; limit — сколько результатов в каждой категории.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
unlike_tracks ~26
Убирает треки из «Мне нравится».
| Name | Type | Req | Description |
|---|---|---|---|
| track_ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Yandex Music (unofficial) MCP server?
Yandex Music (unofficial) runs locally as a PyPI package, launched with uvx yandex-music-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · yandex-music-mcp
claude mcp add kenzolika-yandex-music-mcp -- uvx yandex-music-mcp
What is the Yandex Music (unofficial) MCP server?
Yandex Music (unofficial) is an MCP server listed in the public MCP registry as io.github.kenzolika/yandex-music-mcp. Unofficial Yandex Music server: search, likes, history, My Wave, playlists. Token stays local. This page covers its PyPI package (yandex-music-mcp).
Is the Yandex Music (unofficial) MCP server safe to use?
Yandex Music (unofficial) scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Yandex Music (unofficial) MCP server expose?
Yandex Music (unofficial) exposes 19 tools: account_info, search, get_liked_tracks, get_listening_history, list_my_playlists, and 14 more. Their descriptions and schemas cost roughly 977 tokens of context every time the server is loaded.
Is the Yandex Music (unofficial) MCP server still maintained?
Yandex Music (unofficial) is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Yandex Music (unofficial) MCP server under?
Yandex Music (unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.