CyberStrikeAI — AI Security Testing Platform (MCP)

Main

• Use it only for authorized engagements: validate your scope and keep the platform on a private network; treat logs/audit as part of the deliverable.

• Start with the built-in one-command deploy, then configure an OpenAI-compatible endpoint in Settings before running any orchestration workflows.

• Keep integrations minimal at first: prove MCP stdio mode works with your client, then add plugins (e.g., Burp extension) only when needed.

Source-backed notes

• README provides a one-command deployment: chmod +x run.sh && ./run.sh, and lists Go 1.21+ and Python 3.10+ as prerequisites.
• README describes native MCP support with multiple transports (HTTP/stdio/SSE) and a password-protected web UI with audit logs.
• README notes first-time configuration requires setting an OpenAI-compatible API key/base URL/model before use.

FAQ

• Is it safe to run on a public host?: Treat it as an internal tool: run on private networks and enable auth (README mentions password-protected UI).
• Do I need to install 100+ tools first?: No — start with the core platform; README treats tool installs as optional and incremental.
• Can I use it with my MCP client?: Yes — README lists MCP transports including stdio; test with a minimal workflow first.