Developer · Remote MCP server

MCP Yoto

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

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.danpillay87/mcp-yoto
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-14
Updated
2026-09-14
Publisher
danpillay87 (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/danpillay87) · how
Repository
github.com/danpillay87/mcp-yoto
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp-yoto.danpillay87.workers.dev/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npmmcp-yoto0.1.0stdioNone declared

How to connect MCP Yoto

MCP Yoto is a remote MCP server: there is nothing to install. Its endpoint is https://mcp-yoto.danpillay87.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: mcp-yoto version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mcp-yoto@0.1.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp-yoto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-yoto@0.1.0"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
MCP VS CodeA self-hosted VS Code workbench embedded as an interactive MCP App.Local · stdionpm: @mario.andreschak/mcp-vscode
MCP Whatsapp CloudMCP server for WhatsApp Cloud API (Meta) - messages, media, and templates via Graph API.Local · stdionpm: @codespar/mcp-whatsapp-cloud
MCP Whoisxmlapi32 WHOIS, DNS, IP, threat intelligence, email, and bulk tools for AI agents via WhoisXML API.Local · stdionpm: @whoisxmlapidotcom/mcp-whoisxmlapi
MCP X402 AcceptSelf-hosted MCP proxy that puts an x402 paywall in front of an existing MCP server.Local · stdionpm: @cryptoapis-io/mcp-x402-accept
MCP ZAP ServerSafe, self-hosted ZAP operator for guided AI security scans and reports.Local · HTTPOCI image (Docker): ghcr.io/dtkmn/mcp-zap-server:v0.14.0
MCP ZuulZuul CI - build failure analysis, log search, pipeline status, and job configuration.Local · stdioPyPI: mcp-zuul
mcp-anythingMeta-MCP gateway: search, inspect and call any MCP server from the public registries.Local · stdionpm: mcp-anything
mcp-armorSecurity sidecar for MCP servers: 11 read-only control-plane tools for prompt-injection checks.Local · stdioOCI image (Docker): ghcr.io/studiomeyer-io/mcp-armor:0.8.1