Ryvo Protocol MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

  const result = childProcess.spawnSync(command, parts, {

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  const result = childProcess.spawnSync(command, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ryvo-protocol -- npx -y @ryvonetwork/protocol-mcp

{
  "mcpServers": {
    "ryvo-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@ryvonetwork/protocol-mcp"
      ]
    }
  }
}

[mcp_servers.ryvo-protocol]
command = "npx"
args = ["-y", "@ryvonetwork/protocol-mcp"]

{
  "mcpServers": {
    "ryvo-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@ryvonetwork/protocol-mcp"
      ]
    }
  }
}

{
  "servers": {
    "ryvo-protocol": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ryvonetwork/protocol-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: SOLANA_DEVNET_RPC_URL (Optional Solana devnet RPC URL), RYVO_PROTOCOL_PROGRAM_ID (Optional Ryvo Protocol program ID. Defaults to the live devnet deployment), RYVO_PROTOCOL_DEVNET_USDC_TOKEN_ID (Official devnet USDC token ID in the deployed Ryvo token registry).