three.ws Agent Payments MCP Server

What the code does

We read the source, 14 h 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.

        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.

        const r = await redis.eval(

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

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

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

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

    return subprocess.run(

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

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

    'UklGRmQBAABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZGF0YUABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA…

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

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

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

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

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

Optional settings from the registry entry, left out of the block above: THREE_WS_SESSION (Your three.ws session token (value of the `__Host-sid` cookie from a signed-in browser). Required for account management operations: create_payment_session, list_payment_sessions, check_payment_session, cancel_payment_session), PAYMENT_SESSION_TOKEN (A payment session bearer token (starts with 'pss_') from create_payment_session. Used by the agent for pay_with_session calls when no inline token is passed. Treat like a spending card — it authorizes payments up to the session's budget), THREE_WS_BASE (Base URL of the three.ws API. Override only when self-hosting or targeting a preview deployment), THREE_WS_TIMEOUT_MS (Per-request HTTP timeout in milliseconds. x402 payments involve on-chain settlement so this should be generous (default: 30000)).