Repository navigation
v0.4.2
Fixed
npx -y @asitis/mcpfailed with "could not determine executable to run" from 0.3.0 on. 0.3.0 added a second command (asitis) next to the server (asitis-mcp), and with two commands npx only starts the one named after the package,mcp, which didn't exist. That's the line in the README and the command MCP Registry clients run, so anyone who installed the server that way since 0.3.0 hit the error. The package now has a third command,mcp, which is the server, and the plain form works again.npx -y -p @asitis/mcp asitis-mcpandnpx -y -p @asitis/mcp asitis lintkeep working as before. Nothing changes for the Claude Code plugin or the GitHub Action, which never used npx.asitis-mcp --helplistsload_planand shows the-pform that works on every version.- The README no longer says no real finding was lost between 0.3.0 and 0.4.0. The 0.4.0 precision numbers stand (70% to 91% on 71 hand-labelled repos). The agnix rule count in the comparison table is 761 now.
If you're on 0.3.x to 0.4.1 and an MCP client config runs npx -y @asitis/mcp@<version>, either bump it to 0.4.2 or use npx -y -p @asitis/mcp@<version> asitis-mcp.
Details: packages/mcp/CHANGELOG.md and plugins/asitis/CHANGELOG.md.