Hostile-Command-Suite logo

Hostile-Command-Suite

by cycloarcane

Hostile-Command-Suite (HCS) is an extensible set of command-line micro-services for open-source intelligence and penetration-testing workflows. Each tool is wrapped in a fastMCP façade so a chatbot (or any JSON-RPC client) can drive it securely and receive structured JSON back.

View on GitHub

Last updated: N/A

What is Hostile-Command-Suite?

Hostile-Command-Suite (HCS) is a collection of command-line micro-services designed for open-source intelligence (OSINT) and, soon, penetration testing. It wraps various tools with a fastMCP façade, allowing interaction through chatbots or any JSON-RPC client, and stores results in a PostgreSQL database.

How to use Hostile-Command-Suite?

The suite can be installed manually or using the provided install_hcs.sh script. After installation, configure necessary API keys and environment variables. Tools can then be launched individually via their MCP wrappers using JSON-RPC requests. See the README for detailed instructions and examples.

Key features of Hostile-Command-Suite

  • Extensible architecture

  • Command-line interface

  • JSON-RPC interface for chatbot integration

  • PostgreSQL storage for results

  • Wrappers for popular OSINT tools (Mosint, Sherlock, PhoneInfoga)

  • Automated installation script

Use cases of Hostile-Command-Suite

  • Automated OSINT data gathering

  • Integration with chatbots for security workflows

  • Vulnerability assessment

  • Email intelligence gathering

  • Username and phone number reconnaissance

FAQ from Hostile-Command-Suite

What is MCP?

MCP refers to the micro-services architecture used to wrap the tools, enabling secure and structured communication.

What tools are currently supported?

Currently, the suite includes wrappers for Mosint, Holehe, h8mail, Sherlock, and PhoneInfoga. More tools are planned.

Do I need API keys to use all the tools?

Some tools require API keys for full functionality. Refer to the API-Key Matrix in the README for details.

How do I contribute to the project?

Fork the repository, make your changes, and submit a pull request. Follow the contribution guidelines outlined in the README.

Is there a Docker image available?

A Docker-compose setup is planned for future releases.