three.ws Portfolio MCP Server

What the code does

We read the source, 22 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token',

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        UPDATE destination_whitelist_settings
        SET cooldown_seconds = ${ch.cooldown_seconds ?? row.cooldown_seconds},

        const r = await redis.eval(

        const proc = spawn(ffmpegPath(), ['-hide_banner', '-loglevel', 'error', '-i', 'pipe:0', ...args, 'pipe:1']);

                return JSON.parse(await readFile(path.join(base, rel), 'utf8'));

        lambda: subprocess.run(

COPY --parents package.json package-lock.json .npmrc* **/package.json /app/

            if (reset) { state.cursor = null; state.total = 0; grid.innerHTML = skeletons(); stateEl.hidden = true; }

        `https://api.telegram.org/bot${cfg.token}/sendMessage`,

    "bytecode": "0x60806040523480156200001157600080fd5b5060405162000dd238038062000dd2833981016040819052620000349162000351565b8383600362000044838262000477565b50600462000053828262000477565b5050506001600160a01b038116620000a65760405162461bcd60e51b8152602060048201526011602482015270726…

import { existsSync, mkdirSync, readdirSync, statSync } from 'fs'

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 portfolio-mcp -e 'SOLANA_SECRET_KEY=<SOLANA_SECRET_KEY>' -- npx -y @three-ws/portfolio-mcp

{
  "mcpServers": {
    "portfolio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/portfolio-mcp"
      ],
      "env": {
        "SOLANA_SECRET_KEY": "<SOLANA_SECRET_KEY>"
      }
    }
  }
}

[mcp_servers.portfolio-mcp]
command = "npx"
args = ["-y", "@three-ws/portfolio-mcp"]
env = { SOLANA_SECRET_KEY = "<SOLANA_SECRET_KEY>" }

{
  "mcpServers": {
    "portfolio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/portfolio-mcp"
      ],
      "env": {
        "SOLANA_SECRET_KEY": "<SOLANA_SECRET_KEY>"
      }
    }
  }
}

{
  "servers": {
    "portfolio-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/portfolio-mcp"
      ],
      "env": {
        "SOLANA_SECRET_KEY": "<SOLANA_SECRET_KEY>"
      }
    }
  }
}

Put your own value in place of <SOLANA_SECRET_KEY> (Base58-encoded Solana secret key for the wallet that send_transfer signs from. REQUIRED for send_transfer (the only write tool); a per-call `secret` arg overrides it. Not needed for any read tool. Treat like cash). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: THREE_WS_BASE (Base URL of the three.ws API that serves the portfolio + trades endpoints. Override only when self-hosting or targeting a preview deployment), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the live three.ws API reads), THREE_WS_SESSION (Your three.ws session token (the value of the `__Host-sid` cookie from a signed-in browser). Required for the account-scoped reads — get_portfolio_summary, get_portfolio_history, get_portfolio_asset — which return data for the agents YOU own. The public trade feed and on-chain balance reads do not need it. Treat like a password), SOLANA_RPC_URL (Solana mainnet RPC endpoint used by get_wallet_balances and send_transfer. Defaults to https://api.mainnet-beta.solana.com — bring your own (Helius / Quicknode / Triton) for production traffic), MAX_SOL_PER_TX (Per-transaction spend cap in SOL for native SOL transfers via send_transfer. Bounds the blast radius of a leaked key or an injected argument), RECIPIENT_ALLOWLIST (Optional comma-separated base58 pubkeys. When set, send_transfer refuses any recipient not in the list), REQUIRE_CONFIRM (When on (default), send_transfer refuses until re-issued with confirm:true. Set 0/false to disable the gate).