$ loading_
Scan self-hosted configs to detect security risks in Docker, tunnels, and env files.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "selfhosted-doctor" yet — see the docs or source repo.
Scan the docker-compose.yml in this project and identify possible security risks such as exposed sensitive ports, privileged mode, and weak default settings. List them by severity.
A severity-ranked risk list with the exact config items involved and remediation suggestions.
Review the Cloudflare Tunnel configuration and assess whether there is unnecessary public exposure, routing mistakes, or settings that may leak services.
Potential exposure points in the tunnel config, risk explanations, and safer configuration recommendations.
Scan the repository’s .env files for plaintext secrets, weak passwords, default credentials, or other insecure environment variable practices.
A risk summary of sensitive variables, highlighting what should be rotated, removed, or moved to secret management.
Scan MCP servers for common security risks and assign A-F grades.
Scan MCP servers for runtime, static, config, dependency, and compliance risks.
Scan MCP server configs for injections, secrets, and dangerous commands.
Scan codebases for secrets, SAST issues, vulnerable dependencies, and IaC risks.
Scan code for security risks before commits with automated review assistance.
Scan remote MCP servers for protocol, security, and TLS issues.