cloudlab-mcp

The server handles CloudLab JWT tokens securely by prioritizing environment variables and local file paths, with clear warnings against committing them to version control. It communicates with the CloudLab API exclusively over HTTPS. No 'eval', code obfuscation, or directly malicious patterns were identified in the provided source code. The server operates via standard I/O (stdio), meaning it does not open its own network ports directly, relying on the invoking application (e.g., Claude Desktop) for communication security. Minor risk: CloudLab API error messages are returned directly and could potentially contain detailed backend information, though this is dependent on the CloudLab API itself.