openvds-mcp-server

The server's core functionality involves dynamically launching subprocesses (MCP servers for different VDS profiles) based on a `vds-profiles.json` configuration file. While this design enables profile switching, it introduces a critical dependency on the integrity of this configuration file. If a local attacker can modify `vds-profiles.json` to specify arbitrary commands or arguments, they could achieve code execution. For remote attackers, the risk is mitigated as the API endpoint for profile switching only allows selecting from pre-defined profiles, not creating new ones with arbitrary commands. No direct `eval` or `os.system` calls with unsanitized user input were observed. Sensitive credentials like `ANTHROPIC_API_KEY` are managed via environment variables, which is a good practice. Network communication with Elasticsearch and Anthropic API uses standard libraries.