pkgxray MCP Server

What the code does

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

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.

  { rel: ".aws/credentials", slug: "aws", build: (t) =>

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 file = path.join(CACHE_DIR, cacheKeyFor(name, version));

    const child = spawn(command, args, { stdio: ["ignore", "pipe", "pipe"], ...options });

  /(?:^|\/)\.npmrc$/

  "webhook.site", "pastebin.com", "hastebin", "transfer.sh",

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 pkgxray -- npx -y pkgxray

{
  "mcpServers": {
    "pkgxray": {
      "args": [
        "-y",
        "pkgxray"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.pkgxray]
command = "npx"
args = ["-y", "pkgxray"]

{
  "mcpServers": {
    "pkgxray": {
      "args": [
        "-y",
        "pkgxray"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "pkgxray": {
      "args": [
        "-y",
        "pkgxray"
      ],
      "command": "npx"
    }
  }
}