mcpx connects to programs that may handle credentials, run arbitrary code, or fetch private data. Treat that surface area accordingly.
- No telemetry. No phone-home, no opt-in either.
- No third-party network calls. mcpx only talks to the MCP servers you ask it to connect to.
- Local recordings. Saved sessions live in
~/.local/share/mcpx/recordings/(or$MCPX_DIR/recordings/). - Automatic redaction. Field names matching common credential
patterns (
api_key,apikey,token,password,secret,cookie,authorization,x-api-key) are replaced with<REDACTED>before recordings are written. Not a substitute for hygiene.
mcpx connect "<command>" spawns the command. Connecting to a server you
don't trust is equivalent to running it. A future version intends to
integrate bubblewrap (Linux) and sandbox-exec (macOS).
Email or open a private GitHub security advisory. We aim to acknowledge within two business days. POCs welcome. Reporters credited (with consent) in release notes.
- Zero runtime dependencies.
- No build step. Code you read is code that runs.