Get the FREE Ultimate OpenClaw Setup Guide →

ai4eh

AI for Ethical Hacking - Workshop

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio ethiack-ai4eh docker run -i ethiack/ai4eh:latest \
  --env ENV_FILE_HINT="path/to/env_file (optional; can be used with --env-file if you prefer a file-based approach)" \
  --env GEMINI_API_KEY="your_gemini_api_key_here" \
  --env OPENAI_API_KEY="your_openai_api_key_here"

How to use

The ai4eh MCP server provides a containerized environment that hosts the AI for Ethical Hacking workshop tools. When run, it exposes a suite of security-focused AI utilities and standard security tooling inside a Docker image. Core capabilities include AI-assisted reconnaissance, automated content discovery for fuzzing, intelligent analysis of screenshots, and integration with common security tools via pre-installed components. This MCP setup is designed to help you explore how AI agents can assist with vulnerability discovery, targeted enumeration, and orchestration of tools like nuclei, ffuf, and Subfinder within a single environment.

How to install

Prerequisites:

  • Docker installed and running on your host
  • Access to the ai4eh Docker image (ethiack/ai4eh:latest) from Docker Hub
  • API keys for AI services (e.g., OpenAI, Gemini) if you plan to use AI providers inside the tools

Install steps:

  1. Pull and run the container locally:
docker pull ethiack/ai4eh:latest
  1. Run the container directly (with an env file if you have credentials):
docker run --rm -it --env-file path/to/env_file ethiack/ai4eh:latest
  1. Alternatively, start using the container and pass individual environment variables:
docker run --rm -it -e OPENAI_API_KEY=your_openai_key_here -e GEMINI_API_KEY=your_gemini_key_here ethiack/ai4eh:latest
  1. Verify access to the included tools and scripts inside the container. Typical entry points include the Python scripts and the integrated toolchain referenced in the repository README.

Additional notes

Tips and caveats:

  • If you use --env-file, ensure it contains OPENAI_API_KEY and GEMINI_API_KEY entries as needed. The image expects credentials to access AI services.
  • The container includes a suite of security tools (Nuclei, FFUF, Subfinder, HTTPx, Notify, EyeBaller, PureDNS). Familiarize yourself with each tool's usage and integration points within the AI workflow.
  • For environmental compatibility, ensure Docker has enough CPU/RAM to run AI workloads; consider tuning resource limits if necessary.
  • When sharing across teams, avoid embedding secret keys in images; prefer mounting an env_file or passing environment variables at runtime.

Related MCP Servers

Sponsor this space

Reach thousands of developers