MCP server + Ollama-driven autonomous penetration testing client. Connects LLMs to security tools (nmap, nikto, sqlmap, dalfox…) via Model Context Protocol with session management, output parsing, and findings persistence.
MCPpedia last refreshed this data
Mcpstrike is an MCP server that MCP server + Ollama-driven autonomous penetration testing client. Connects LLMs to security tools (nmap, nikto, sqlmap, dalfox…) via Model Context Protocol with session management, output parsing, and findings persistence. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 65/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcpstrike": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
mcpstrike connects an LLM (via Ollama) to security tools through the Model Context Protocol (MCP), enabling autonomous or guided penetration testing from a terminal interface.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
autonomous_pentestGenerate an autonomous penetration test prompt for a target
guided_pentestGenerate a guided penetration test prompt with domain specification
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
Regression testing for MCP servers. Checks capabilities, invokes tools, detects schema drift.
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
MCP Security Weekly
Get CVE alerts and security updates for Mcpstrike and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
mcpstrike connects an LLM (via Ollama) to security tools through the Model Context Protocol (MCP), enabling autonomous or guided penetration testing from a terminal interface.
mcpstrike-client mcpstrike-server (MCP) hexstrike_server
(TUI + Ollama) ---> (FastMCP, port 8889) ---> (port 8888, must be running)
|
v
Ollama LLM
(llama3.2, qwen3.5, etc.)
Optional: mcpstrike-backend can replace hexstrike_server for local testing
Components:
| Component | Role | Default port |
|---|---|---|
| hexstrike_server | External backend — must be started separately | 8888 |
mcpstrike-server | MCP server exposing 15 tools for session/command management | 8889 |
mcpstrike-client | Interactive TUI that drives an Ollama LLM to call MCP tools | — |
mcpstrike-backend (optional) | Lightweight local alternative to hexstrike_server | 8890 |
Install mcpstrike in a project-local virtual environment. Its Python dependencies and all command-line entry points stay isolated from the system Python.
git clone https://github.com/ente0/mcpstrike.git
cd mcpstrike
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e .
Install the optional standalone backend in the same environment:
python -m pip install -e ".[backend]"
For development tools and the standalone backend:
python -m pip install -e ".[dev,backend]"
After pulling changes, refresh the active environment:
git pull
python -m pip install -e ".[dev,backend]"
While .venv is active, mcpstrike, mcpstrike-server,
mcpstrike-client, mcpstrike-prompt and mcpstrike-backend are already on
your PATH. To use them from any directory without activating the environment,
run this from the repository root once:
printf '\nexport PATH="%s/.venv/bin:$PATH"\n' "$PWD" >> ~/.zshrc
source ~/.zshrc
For Bash, replace ~/.zshrc with ~/.bashrc in both commands. The command
stores the repository's absolute .venv/bin path; recreate the environment if
you move the repository.
Leave the environment when finished:
deactivate
hexstrike_server must already be running on port 8888 before starting mcpstrike.
mcpstrike
mcpstrike is the stack launcher. It opens three tiled xterm windows (or falls back to tmux, then background processes). All options can be overridden via flags:
mcpstrike --model qwen3:8b
mcpstrike --ollama-url http://10.0.0.5:11434
mcpstrike --sessions-dir /opt/pentest/sessions
mcpstrike --font-size 15 --screen-width 2560 --screen-height 1440
mcpstrike --tmux # force tmux even if DISPLAY is set
See mcpstrike --help for all options.
Note:
start.sh/my_start.share still available as personal launcher scripts with hardcoded IPs/model names.
# Terminal 1: MCP server (points to hexstrike_server on 8888)
HEXSTRIKE_BACKEND_URL=http://localhost:8888 mcpstrike-server
# Terminal 2: Client
mcpstrike-client --ollama-url http://<ollama-host>:11434 --model qwen3.5