mcp-github-app-auth

The core server logic handles environment variables for credentials and uses `subprocess.run` with list arguments for Git commands, which is generally safe. However, the `mcp_test.sh` script uses `eval "$SERVER_CMD"` where `SERVER_CMD` is constructed using environment variables. This creates a shell injection vulnerability if `GITHUB_PRIVATE_KEY` or other `GITHUB_*` environment variables contain malicious shell metacharacters. While this `eval` is confined to a testing script and not the primary server execution path (e.g., direct `python` execution or the recommended `docker run` from the README), it represents a significant security oversight in the repository's practices. There are no hardcoded secrets or obfuscation found. Network communication relies on standard HTTPS with GitHub API.