walkerOS Source Browser MCP Server

What the code does

We read the source, 5 d 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.

  const packageDir = path.join(targetDir, 'node_modules', localPkg.name);

        dom.window.eval(snapshotCode);

    path.join(homeDir, '.npmrc'),

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 source-browser -- npx -y @walkeros/mcp-source-browser

{
  "mcpServers": {
    "source-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@walkeros/mcp-source-browser"
      ]
    }
  }
}

[mcp_servers.source-browser]
command = "npx"
args = ["-y", "@walkeros/mcp-source-browser"]

{
  "mcpServers": {
    "source-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@walkeros/mcp-source-browser"
      ]
    }
  }
}

{
  "servers": {
    "source-browser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@walkeros/mcp-source-browser"
      ]
    }
  }
}