io.github.danpillay87/mcp-yoto
NPM · MCP-YOTO · 2 COMPONENTS
MCP server for Yoto: manage cards, tracks, icons and family devices from any MCP client.
Available components
Last scanned (3 hours ago)
Scores higher than 66% of npm 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 Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 0 of 17 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 51 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1140 tokens (~71/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
- 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 28 Oct 26 +1
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 −4
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/mcp-yoto@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| 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 →
yoto_add_track Add a track to a Yoto card ~116
Uploads an audio file and appends it as a new chapter/track on an existing MYO card. Runs locally, so it takes a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| audioFilePath | string | yes | Absolute path to a local audio file (MP3, M4A/AAC, WAV, or OGG). |
| cardId | string | yes | – |
| iconRef | string | – | A yoto:#<mediaId> icon reference, e.g. from yoto_upload_icon. |
| trackTitle | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
yoto_create_card Create a new Yoto card ~93
Creates a new MYO card with the given title, and optionally an initial set of tracks (each a mediaRef from yoto_upload_audio, one track per chapter) and a default icon for those chapters.
| Name | Type | Req | Description |
|---|---|---|---|
| iconRef | string | – | A yoto:#<mediaId> icon reference, e.g. from yoto_upload_icon. |
| title | string | yes | – |
| tracks | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
yoto_delete_card Delete a Yoto card ~53
Permanently deletes a MYO card from the parent's Yoto library. Requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| confirm | boolean | yes | Must be true -- this permanently deletes the card. |
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| deleted | boolean | yes | – |
No examples provided.
yoto_get_card Get a Yoto card's details ~34
Fetches one MYO card's full details, including every chapter and track.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
yoto_get_device_config Get a Yoto device's configuration ~73
Fetches one player's device configuration (clock face, volume limits, right-hand-button shortcuts, etc). This is a beta Yoto endpoint that needs a device-management scope this server intentionally never requests, so expect a FORBIDDEN_SCOPE result with a hint rather than data.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
No examples provided.
yoto_list_cards List your Yoto cards ~79
Lists cards in your own MYO (Make Your Own) library, or the shared family library's groups. Family groups are collections, not individual cards -- see the returned note when source is "family".
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Reserved for future pagination; currently unused. |
| limit | integer | – | – |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | – | – |
| groups | array | – | – |
| note | string | – | – |
| source | string | yes | – |
No examples provided.
yoto_list_devices List your Yoto devices ~29
Lists the family's Yoto players -- name, online status, and device type. View-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | yes | – |
No examples provided.
yoto_search_icons Search Yoto's icon catalogue ~87
Searches Yoto's public catalogue of 16x16 pixel-art icons by title or tag, for use as a chapter/track icon (iconRef) when creating or updating a card.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Free-text match against the icon's title and tags. |
| tags | array | – | Icon must carry every one of these tags. |
| Name | Type | Req | Description |
|---|---|---|---|
| icons | array | yes | – |
No examples provided.
yoto_sign_in Sign in to Yoto ~98
CLI mode: launches a local PKCE sign-in flow (opens your browser to Yoto's login page and waits for the callback). Remote mode: this connector runs on a server with nothing to launch, so it returns instructions to sign in from your AI client's connector settings instead -- that flow redirects to Yoto's own login page too.
| Name | Type | Req | Description |
|---|---|---|---|
| openBrowser | boolean | – | CLI only: open the sign-in URL automatically. Default true. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| url | string | – | – |
No examples provided.
yoto_sign_out Sign out of Yoto ~83
CLI mode: deletes the locally stored Yoto credential (keychain or file). Remote mode: this server never stores your Yoto token at all, so it returns instructions for disconnecting from your AI client and revoking access at Yoto directly. Requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true -- this clears your stored Yoto credential. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
No examples provided.
yoto_status Check Yoto sign-in status ~50
Reports whether this connection is signed in to Yoto, which mode it's running in (cli or remote), where the credential is stored, its granted scopes, and whether the Yoto API is currently reachable.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apiReachable | boolean | – | – |
| expiresAt | number | – | – |
| hint | string | – | – |
| mode | string | yes | – |
| scopes | array | – | – |
| signedIn | boolean | yes | – |
| tokenStore | string | – | – |
No examples provided.
yoto_update_card Update a Yoto card ~81
Shallow-merges patch fields (e.g. title, or a full replacement content.chapters array to rename/reorder tracks or set icons) onto an existing card, then saves it.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | – |
| patch | object | yes | Fields to merge onto the existing card, e.g. { title } or { content }. |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
yoto_upload_audio Upload audio to Yoto ~106
Uploads an audio file to Yoto and waits for it to finish transcoding, returning a yoto:#<sha256> mediaRef usable as a track when creating or updating a card. Runs locally, so it takes a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| audioFilePath | string | yes | Absolute path to a local audio file (MP3, M4A/AAC, WAV, or OGG). |
| loudnorm | boolean | – | Apply loudness normalisation. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | – |
| fileSize | number | – | – |
| format | string | – | – |
| mediaRef | string | yes | – |
No examples provided.
yoto_upload_icon Upload a custom Yoto icon ~117
Uploads a custom 16x16 pixel-art icon to your Yoto account, returning a mediaId usable as an iconRef on cards and tracks. Runs locally, so it takes a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| autoConvert | boolean | – | Let Yoto auto-convert the image to its 16x16 icon format. Default false. |
| imagePath | string | yes | Absolute path to a local image file (PNG, JPEG, or SVG). |
| title | string | yes | Sent to Yoto as the uploaded file's name. |
| Name | Type | Req | Description |
|---|---|---|---|
| mediaId | string | yes | – |
| url | string | – | – |
No examples provided.
How do I install the io.github.danpillay87/mcp-yoto server?
io.github.danpillay87/mcp-yoto runs locally as an npm package, launched with npx -y mcp-yoto. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-yoto
claude mcp add danpillay87-mcp-yoto -- npx -y mcp-yoto
What is the io.github.danpillay87/mcp-yoto server?
io.github.danpillay87/mcp-yoto is listed in the public MCP registry as io.github.danpillay87/mcp-yoto. MCP server for Yoto: manage cards, tracks, icons and family devices from any MCP client. This page covers its npm package (mcp-yoto).
Is the io.github.danpillay87/mcp-yoto server safe to use?
io.github.danpillay87/mcp-yoto scores 80 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.danpillay87/mcp-yoto server expose?
io.github.danpillay87/mcp-yoto exposes 14 tools: yoto_status, yoto_sign_in, yoto_sign_out, yoto_list_cards, yoto_get_card, and 9 more. Their descriptions and schemas cost roughly 1,099 tokens of context every time the server is loaded.
Is the io.github.danpillay87/mcp-yoto server still maintained?
io.github.danpillay87/mcp-yoto is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.danpillay87/mcp-yoto server under?
io.github.danpillay87/mcp-yoto declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.