{"id":"pwno-io-pwno-mcp","name":"pwno-mcp","af_score":51.8,"security_score":26.0,"reliability_score":31.2,"what_it_does":"pwno-mcp runs GDB (with pwndbg) inside an isolated environment and exposes stateful debugging/exploit I/O workflows to LLM agents via an MCP server, with support for multiple sessions and helper automation.","best_when":"Running locally/privately (e.g., container on a developer machine) where an agent needs stateful debugging and can manage its own session lifecycle.","avoid_when":"When you need strong, documented auth/rate limiting for untrusted remote clients, or when container/ptrace privileges cannot be granted safely.","last_evaluated":"2026-03-30T13:35:57.986130+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["Requires ptrace-capable container execution (SYS_PTRACE/SYS_ADMIN) which may fail depending on host/container security settings.","Statefulness implies agents must manage session lifecycle correctly to avoid cross-session contamination.","Deterministic control depends on correct GDB/MI usage; agents may need to wait for prompt/response boundaries to avoid desync.","Running untrusted binaries under the debug environment can introduce risk beyond the tool’s API surface."],"error_quality":0.0}