SassyMCP MCP Server

What the code does

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

                proc = subprocess.Popen([str(p)] + extra, creationflags=subprocess.DETACHED_PROCESS)

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.

    (".npmrc", "stored credential file"),

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 proc = spawn(cmd, args, { shell: false });

            const candidate = path.join(dir, exeName);

            proc = subprocess.Popen(

        subprocess.Popen(["code", str(repo_root())], shell=True)

                __import__(pkg)

    (".npmrc", "stored credential file"),

                for root, dirs, files in os.walk(p):

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 sassymcp -- uvx sassymcp

{
  "mcpServers": {
    "sassymcp": {
      "command": "uvx",
      "args": [
        "sassymcp"
      ]
    }
  }
}

[mcp_servers.sassymcp]
command = "uvx"
args = ["sassymcp"]

{
  "mcpServers": {
    "sassymcp": {
      "command": "uvx",
      "args": [
        "sassymcp"
      ]
    }
  }
}

{
  "servers": {
    "sassymcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sassymcp"
      ]
    }
  }
}