foxess-mcp-server

The server demonstrates strong security practices including comprehensive input validation, thorough log sanitization, and secure error handling. Disk cache encryption is implemented, but its effectiveness depends on the `cryptography` package being installed and the `FOXESS_CACHE_KEY` environment variable being set; otherwise, it defaults to unencrypted storage. MD5 is used for API signature generation, which is a known cryptographic weakness, but this is a requirement of the FoxESS API and its risk is partially mitigated by the inclusion of a timestamp and HTTPS communication. The internal rate limiter state is not persistent across server restarts, potentially allowing a burst of requests upon reboot.