Quickstart
mcpwn wraps a stdio MCP server: the host launches mcpwn, mcpwn launches the real server and relays the traffic, logging every message to stderr (stdout/stdin stay byte-clean for the protocol).
The 30-second tour
Section titled “The 30-second tour”# Passive X-ray — watch all traffic, change nothingmcpwn -v -- npx -y @modelcontextprotocol/server-filesystem /tmp
# Interactive — hold every message and decide: forward / drop / edit / tampermcpwn -i -- node ./my-server.js
# Tamper headlessly — apply JSON rules to messages in flightmcpwn -r attack.json -- node ./my-server.js
# Record a session log (JSONL) for later reviewmcpwn -l session.jsonl -- node ./my-server.jsSelf-driving scan (no agent in the loop)
Section titled “Self-driving scan (no agent in the loop)”# Drives the handshake, enumerates every surface, samples content, runs all# passive detectors, and fails CI on findings at/above a severity.mcpwn scan --fuzz --findings-out ./out --fail-on high -- node ./my-server.jsmcpwn scan --http https://mcp.example.com/mcp --findings-out ./outTry the bundled demo
Section titled “Try the bundled demo”npm run demo # end-to-end inject -> exfil demo (no network, no API key)npm run dvmcp # the Damn-Vulnerable MCP scoreboardWhere to next
Section titled “Where to next”- Intercept proxy - the Repeater loop, detectors, scope.
- Tamper rules - the JSON rule format and actions.
- Active scan - the agent-free scanner and templates.
- Auditing playbook - threat class → concrete workflow.