splunk-mcp

The setup explicitly disables SSL certificate verification for both the Splunk MCP server and the client-side 'mcp-remote' tool (`CURL_OPTS="-k"`, `ssl_verify=false`, `NODE_TLS_REJECT_UNAUTHORIZED="0"`). While noted for 'local development', this is a critical security vulnerability if used in any non-isolated environment or production, as it exposes data to potential man-in-the-middle attacks. The `README.md` file contains misleading links where all 'additional resources' (Splunk, Docker, 1Password documentation) and 'download' links point to a single zip file (`splunk-mcp-demagog.zip`) on GitHub, rather than their official sources or specific releases. This raises significant trust concerns regarding the integrity of the downloaded components and the installation instructions. Tokens are generated and stored in a file (`.secrets/splunk-token`) and the Claude Desktop config, but are restricted with `chmod 600` and have a 15-day expiry, which are reasonable practices. Secrets are managed securely via 1Password CLI for injection into environment variables.