$THREE Token MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

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.

        await fs.writeFile(out, bytes);

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.

    return redis.eval(ROLLBACK_FLOOR_LUA, [key], [String(delta)]);

                    filePath = path.join(ROOT_PUBLIC, url);

    const child = spawn(command[0], command.slice(1), { stdio: 'inherit', shell: false });

        exec(compile(job["code"], "<three-ws-blender-mcp>", "exec"), namespace)

    const drop = STANDING_HIP_HEIGHT * (root.height - 1) + root.rise;

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

    'UklGRmQBAABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZGF0YUABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA…

const TELEGRAM_API = 'https://api.telegram.org';

    <script type="module" src="https://three.ws/agent-3d/latest/agent-3d.js"></script>

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 three-token-mcp -- npx -y @three-ws/three-token-mcp

{
  "mcpServers": {
    "three-token-mcp": {
      "args": [
        "-y",
        "@three-ws/three-token-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.three-token-mcp]
command = "npx"
args = ["-y", "@three-ws/three-token-mcp"]

{
  "mcpServers": {
    "three-token-mcp": {
      "args": [
        "-y",
        "@three-ws/three-token-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "three-token-mcp": {
      "args": [
        "-y",
        "@three-ws/three-token-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SOLANA_SECRET_KEY (Base58 Solana secret key that signs burns (the wallet that holds the $THREE). Not needed for the read-only tools (three_price, three_balance). Treat like cash.), SOLANA_RPC_URL (Solana mainnet RPC endpoint. Defaults to the public cluster — bring your own (Helius / Quicknode / Triton) for production traffic.), THREE_WS_BASE (Base URL of the three.ws token API (serves /api/token/config and /api/token/price). Override only when self-hosting.), MAX_BURN_USD (Max USD value of $THREE a single three_burn call may destroy.), REQUIRE_CONFIRM (When on (default), three_burn refuses until re-issued with confirm:true. Set 0/false to disable the gate.). The author declared them in the registry entry; get the values from the project itself.