starlink-enterprise-mcp-server

Secrets are loaded from environment variables (STARLINK_CLIENT_ID, STARLINK_CLIENT_SECRET) and are explicitly kept out of version control via `.gitignore`. API authentication uses OAuth2 client credentials with token refresh logic, including a safety buffer before token expiry. HTTP requests are handled by `httpx` with `response.raise_for_status()` for basic error handling. No `eval`, code obfuscation, or explicit malicious patterns were identified in the provided `starlink_mcp_server.py` source code. Input validation at the API call level within the server could be further elaborated, though MCP framework might provide some level of schema enforcement.