three.ws Coin Clash 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.

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

                    filePath = path.join(ROOT_PUBLIC, url);

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

    const [row] = await sql`SELECT voice_provider, voice_id FROM agent_identities WHERE id = ${agentId}`.catch(() => []);

    return subprocess.run(

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

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

    'UklGRmQBAABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZGF0YUABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA…

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

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

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

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

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

{
  "servers": {
    "clash-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/clash-mcp"
      ]
    }
  }
}

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 Coin Clash endpoints. Override only when self-hosting or targeting a preview deployment), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the live Coin Clash reads and writes), SOLANA_SECRET_KEY (Base58 Solana secret key for the enlisting wallet. Required only for the write tools (enlist_faction, rally_faction) — reads work without it. Per-call `secret` arguments override this. The wallet must hold the faction coin it enlists for. Treat like cash).