Runs Docker security audits and container hardening checks against Docker environments.
Uses Falco for runtime security monitoring of cloud-native and containerized workloads.
Enables API security testing workflows focused on GraphQL endpoints.
Manages and inspects Kubernetes Helm chart configurations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ekay Start an authorized engagement on scanme.nmap.org and show me the results."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Use only on assets you own or have written permission to test.
EKay is a local cybersecurity orchestration server that wraps Kali/security binaries and exposes them to AI assistants (Cursor, Claude) over MCP, while running a red-team kill-chain internally.
Layer | Role |
| HTTP API + TriggerBus agents + findings |
| MCP stdio bridge for Cursor / Claude |
Catalog | 223 runnable tools (nmap, nuclei, certipy, …) |
ScopeGuard | Blocks out-of-scope targets before any binary runs |
Evidence | Append-only JSONL for demos / thesis artefacts |
Topic | HexStrike | EKay v2 |
Mental model | Flat tool dump | Kill-chain phases |
Memory | Chat only | Finding graph |
“What next?” | LLM guesses |
|
Concurrency | Mostly sequential LLM calls | TriggerBus parallel agents |
Scope | Easy to leave scope | ScopeGuard on every run |
Dangerous tools | Same path as nmap | Risk classes + |
Red-team depth | Generic scanners | AD / post / cloud modules (Certipy, coerce, linpeas, …) |
Reporting | Ad-hoc paste | Evidence + MITRE tags on findings |
flowchart LR
Cursor["Cursor_or_Claude"] --> MCP["ekay_mcp.py"]
MCP --> API["ekay_server.py"]
API --> Scope["ScopeGuard"]
Scope --> Bus["Phase_TriggerBus"]
Bus --> Tools["Catalog_runners"]
Tools --> Findings["Finding_Graph"]
Findings --> Next["ekay_next_actions"]
Next --> Cursor
Tools --> Evidence["Evidence_JSONL"]Related MCP server: AI-Pentest-MCP
Phase | Purpose | Example tools |
| Passive / open-source intel | subfinder, amass, theHarvester |
| Host & port discovery | nmap, naabu, rustscan |
| Web/API attack surface | httpx, nuclei, katana, nikto |
| Gated foothold sims | SE/phishing-sim (restricted) |
| Credential access (gated) | hydra, netexec, john |
| Active Directory | certipy, bloodhound-python, ldapdomaindump |
| Cloud posture | prowler, trivy, enumerate-iam |
| Host triage | linpeas, winpeas, pspy |
| Evidence packaging | faraday-cli, defectdojo |
MVP auto-run on ekay_start_engagement:osint (optional) → recon (nmap) → external (httpx + nuclei on web ports) → report on finalize.
AD / creds / post phases require EKAY_ALLOW_INTRUSIVE=1 and written authorization.
See the full inventory: docs/TOOLS.md.
git clone https://github.com/rohm8358/ekay.git
cd ekay
python3 -m venv ekay-env
source ekay-env/bin/activate
pip install -r requirements.txt
# optional: install as many Kali binaries as possible
sudo ./scripts/install_kali.sh
# Terminal 1 — real server (shows the banner)
./start-ekay.sh
# or: ./ekay-env/bin/ekay-python ekay_server.pyHealth check (Terminal 2):
curl -s http://127.0.0.1:8787/health | jq .
./ekay-env/bin/ekay-python -m ekay doctor
./ekay-env/bin/ekay-python -m ekay engage 127.0.0.1 --osint~/.cursor/mcp.json){
"mcpServers": {
"ekay": {
"command": "/absolute/path/to/ekay/ekay-env/bin/ekay-python",
"args": [
"/absolute/path/to/ekay/ekay_mcp.py",
"--server",
"http://127.0.0.1:8787"
],
"timeout": 300
}
}
}Keep ekay_server.py running. Restart the MCP connection after config changes.
ekay_health / ekay_doctor
ekay_start_engagement (in-scope target)
ekay_findings → ekay_next_actions
ekay_run_tool / catalog tools for suggested steps
ekay_advance_phase (e.g. ad) when authorized
ekay_finalize → evidence / report summary
Tool | Role |
| Start scoped kill-chain run |
| Structured findings |
| Suggest next tools from findings |
| Move to ad / creds / cloud / … |
| Report summary |
| Phase list + tool counts |
| Filter catalog by phase/family |
| Run one catalog tool |
| Evidence JSONL |
| Architecture diff |
Plus every catalog tool as its own MCP tool (nmap, nuclei, certipy, …).
Count | |
Total (runnable) | 223 |
Removed uninstallable | 23 (Windows-only / heavy platforms / dead projects) |
HexStrike-origin + EKay modules | mixed; see docs/TOOLS.md |
Regenerate docs from source anytime:
./ekay-env/bin/ekay-python scripts/export_catalog.pyHuman-readable: docs/TOOLS.md
Machine-readable: docs/catalog.json
The animation at the top is generated from a live ekay_server.py process (banner + /health + engagement):
./ekay-env/bin/ekay-python scripts/make_demo_gif.py
# writes assets/ekay-server-demo.gif and assets/ekay-server-banner.png./ekay-env/bin/ekay-python -m ekay doctor
./ekay-env/bin/ekay-python -m ekay phases
./ekay-env/bin/ekay-python -m ekay tools --phase ad
./ekay-env/bin/ekay-python -m ekay engage scanme.nmap.org --osint
./ekay-env/bin/ekay-python -m ekay findings --engagement-id <id>
./ekay-env/bin/ekay-python -m ekay next <id>
./ekay-env/bin/ekay-python -m ekay phase <id> ad
./ekay-env/bin/ekay-python -m ekay finalize <id>
./ekay-env/bin/ekay-python -m ekay compareVariable | Default | Meaning |
|
| Bind address |
|
| Bind port |
| localhost + scanme | Allowed targets ( |
|
| Unlock intrusive/restricted + AD/creds phases |
|
| Agent thread pool |
|
| Seconds per binary |
|
| Register all catalog tools on MCP |
| empty | Optional Bearer lock |
Copy .env.example → .env for local defaults (.env is gitignored).
Cursor/Claude product security alerts cannot be removed by EKay. Prefer recon / OSINT / external / report from chat; use gated phases with explicit authorization.
Missing binaries return blocked_reason — install with scripts/install_kali.sh.
EKay does not ship a raw shell API (/api/command).
./ekay-env/bin/ekay-python -m pytest -qEKay wraps local security programs for authorized assessments. Social-engineering, wireless, relay, and credential modules are for approved lab / contracted work only.
This server cannot be deployed
Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.
AI pentesting: run scans, triage vulnerabilities, review PRs, manage schedules and assets.
DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.
Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.
