Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.danpillay87/mcp-yoto

NPM · MCP-YOTO · 2 COMPONENTS · SCANNED SEP 20

MCP server for Yoto: manage cards, tracks, icons and family devices from any MCP client.

72 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • 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 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

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.

Install

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

# add to Claude Code
claude mcp add danpillay87-mcp-yoto -- npx -y mcp-yoto
// .cursor/mcp.json
{
  "mcpServers": {
    "danpillay87-mcp-yoto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yoto"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "danpillay87-mcp-yoto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yoto"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add danpillay87-mcp-yoto -- npx -y mcp-yoto
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danpillay87-mcp-yoto": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-yoto"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add danpillay87-mcp-yoto --command npx --arg -y --arg mcp-yoto
# ~/.hermes/config.yaml
mcp_servers:
  danpillay87-mcp-yoto:
    command: "npx"
    args: ["-y", "mcp-yoto"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "danpillay87-mcp-yoto": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-yoto"
      ]
    }
  }
}
# add to Vellum
assistant mcp add danpillay87-mcp-yoto -t stdio -c npx -a -y mcp-yoto
// mcp.json
{
  "mcpServers": {
    "danpillay87-mcp-yoto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yoto"
      ]
    }
  }
}
Changelog

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.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 57

    First indexed and scored.

Diagnostics

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 20 Sept 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 →

Dependencies 17 packages
Packages resolved 17
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,099 tokens

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 →

Tool Tokens
yoto_add_track ~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.

NameTypeReqDescription
audioFilePathstringyesAbsolute path to a local audio file (MP3, M4A/AAC, WAV, or OGG).
cardIdstringyes
iconRefstringA yoto:#<mediaId> icon reference, e.g. from yoto_upload_icon.
trackTitlestring
NameTypeReqDescription
cardobjectyes

No examples provided.

yoto_create_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.

NameTypeReqDescription
iconRefstringA yoto:#<mediaId> icon reference, e.g. from yoto_upload_icon.
titlestringyes
tracksarray
NameTypeReqDescription
cardobjectyes

No examples provided.

yoto_delete_card ~53

Permanently deletes a MYO card from the parent's Yoto library. Requires confirm: true.

NameTypeReqDescription
cardIdstringyes
confirmbooleanyesMust be true -- this permanently deletes the card.
NameTypeReqDescription
cardIdstringyes
deletedbooleanyes

No examples provided.

yoto_get_card ~34

Fetches one MYO card's full details, including every chapter and track.

NameTypeReqDescription
cardIdstringyes
NameTypeReqDescription
cardobjectyes

No examples provided.

yoto_get_device_config ~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.

NameTypeReqDescription
deviceIdstringyes
NameTypeReqDescription
configobjectyes

No examples provided.

yoto_list_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".

NameTypeReqDescription
cursorstringReserved for future pagination; currently unused.
limitinteger
sourcestring
NameTypeReqDescription
cardsarray
groupsarray
notestring
sourcestringyes

No examples provided.

yoto_list_devices ~29

Lists the family's Yoto players -- name, online status, and device type. View-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
devicesarrayyes

No examples provided.

yoto_search_icons ~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.

NameTypeReqDescription
limitinteger
querystringFree-text match against the icon's title and tags.
tagsarrayIcon must carry every one of these tags.
NameTypeReqDescription
iconsarrayyes

No examples provided.

yoto_sign_in ~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.

NameTypeReqDescription
openBrowserbooleanCLI only: open the sign-in URL automatically. Default true.
NameTypeReqDescription
messagestringyes
urlstring

No examples provided.

yoto_sign_out ~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.

NameTypeReqDescription
confirmbooleanyesMust be true -- this clears your stored Yoto credential.
NameTypeReqDescription
messagestringyes

No examples provided.

yoto_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.

NameTypeReqDescription
apiReachableboolean
expiresAtnumber
hintstring
modestringyes
scopesarray
signedInbooleanyes
tokenStorestring

No examples provided.

yoto_update_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.

NameTypeReqDescription
cardIdstringyes
patchobjectyesFields to merge onto the existing card, e.g. { title } or { content }.
NameTypeReqDescription
cardobjectyes

No examples provided.

yoto_upload_audio ~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.

NameTypeReqDescription
audioFilePathstringyesAbsolute path to a local audio file (MP3, M4A/AAC, WAV, or OGG).
loudnormbooleanApply loudness normalisation. Default false.
NameTypeReqDescription
durationnumber
fileSizenumber
formatstring
mediaRefstringyes

No examples provided.

yoto_upload_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.

NameTypeReqDescription
autoConvertbooleanLet Yoto auto-convert the image to its 16x16 icon format. Default false.
imagePathstringyesAbsolute path to a local image file (PNG, JPEG, or SVG).
titlestringyesSent to Yoto as the uploaded file's name.
NameTypeReqDescription
mediaIdstringyes
urlstring

No examples provided.

Common questions

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 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.