Pixelcheck MCP Server

What the code does

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

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.

postinstall: node scripts/postinstall.mjs

  return path.join(root, newest, `chrome-${token}`, exeName);

      execFileSync(cmd, args, { stdio: "ignore" });

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

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

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

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

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

This one needs environment variables set before it will start: ANTHROPIC_API_KEY (Anthropic API key. Required for LLM-backed primitives (judge, extract-with-schema) and the audit_url / explore_url presets. Meta tools (list_personas, list_scenarios, get_last_report) work without it.). The author declared them in the registry entry; get the values from the project itself.