MCP server wrapper for Commix — Command injection exploitation.
Commix (commix) is a security tool that provides: Command injection exploitation.
See commixproject/commix for full documentation.
No API keys required — Commix runs locally inside the Docker container.
Summary. MCP server wrapper for Commix — Command injection exploitation.
Tools:
run_commix — Run commix with the given arguments. Returns structured JSON output.run_commixRun commix with the given arguments. Returns structured JSON output.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
arguments | string | Yes | — | Command-line arguments (e.g. "--help") |
timeout_seconds | integer | No | 600 | Maximum execution time in seconds |
{
"raw": "commix output will appear here"
}
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
docker-compose up -d
docker run -i --rm hackerdogs/commix-mcp:latest
docker run -d -p 8225:8225 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8225 \
hackerdogs/commix-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"commix-mcp": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/commix-mcp:latest"],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"commix-mcp": {
"url": "http://localhost:8225/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8225 | HTTP port (only used with streamable-http) |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly (e.g. "Use naabu to scan example.com"). If you don't specify, Hackerdogs will automatically choose the best tool for the job — it may choose this one on its own.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/commix-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name commix-mcp-test -p 8225:8225 \
-e MCP_TRANSPORT=streamable-http \
hackerdogs/commix-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8225/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8225/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. Call a tool:
curl -s -X POST http://localhost:8225/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_commix","arguments":{"arguments":"--help"}}}'
4. Clean up:
docker stop commix-mcp-test
You can run the commix CLI in the same container by overriding the entrypoint to test for command injection without starting the MCP server.
Test a URL:
docker run -i --rm --entrypoint commix hackerdogs/commix-mcp:latest -u "https://example.com/page?cmd=test"
Show help:
docker run -i --rm --entrypoint commix hackerdogs/commix-mcp:latest --help
Content type
Image
Digest
sha256:704fc7696…
Size
107.2 MB
Last updated
4 months ago
docker pull hackerdogs/commix-mcp