Offense MCP Server

The Offense CLI and MCP proxy code shows careful credential handling, including owner-only config directories, no symlink following, refusal of credentialed redirects, endpoint binding for API keys, budget gating before paid uploads, and secret scrubbing from output. Network access, local file writes, and subprocess spawning for browser launch and Docker/Kubernetes collection match the stated security-tooling purpose, and the only concerns are minor (the truncated code limits full review of the MCP proxy and hosted upload paths). The server is judged acceptable for the Developer Tools category, with the main caution being the broad local execution of collectors and the paid/upload flows that should be reviewed before use. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity).

8 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.