agent-hellboy/mcpfz-probe — explained in plain English
Analysis updated 2026-05-18
Monitor an MCP server's real system behavior during automated fuzz testing.
Attribute suspicious actions like network connections or file deletions to the exact tool call that caused them.
Test fuzzing pipelines without root access using the deterministic fake backend.
Catch security issues like shell execution or sensitive file reads in a vulnerable MCP server on Linux.
| agent-hellboy/mcpfz-probe | 132ikl/game | 1lystore/pay-dcp | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Rust | Rust | Rust |
| Last pushed | — | 2020-12-30 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
The real eBPF backend needs a BTF-enabled Linux kernel, root or CAP_BPF, and a nightly Rust toolchain with LLVM dev libraries.
This is a security testing companion tool. It works alongside a separate project called mcp-server-fuzzer, which is a tool that automatically tests MCP servers, the services AI assistants call out to, by sending them unexpected or malformed inputs to look for bugs and security holes. While that fuzzer handles starting the process being tested and timing each call, this project watches what actually happens on the computer while each call runs, and connects those observed events back to the specific call that caused them. It is split into two parts. A small Rust program, called the sidecar, does the actual low level watching, since Rust is well suited for a small, easily checked, high performance program. A Python library handles coordinating with the fuzzer and deciding whether an observed event counts as a problem. The watching itself works two ways. A simple fake mode replays a scripted set of events for testing purposes, requiring no special system permissions and running on any operating system. A real mode, available only on Linux, uses a kernel technology called eBPF to directly observe system calls such as starting a new program, opening a network connection, opening or deleting a file, or attaching a debugger to a process. This real mode has been tested against a deliberately vulnerable example server and successfully caught it running shell commands, reading sensitive files, connecting out over the network, and manipulating files, attributing each of these actions to the exact tool call that triggered it. Developers using the two tools together turn this monitoring on with a few environment variables, and the fuzzer's final report then includes these kernel level findings alongside its usual results. The project includes both Python and Rust test suites and documentation covering its communication protocol and internal architecture.
A runtime security probe that watches what an MCP server actually does on the system while it's being fuzz tested, and ties each action back to the tool call that caused it.
Mainly Rust. The stack also includes Rust, Python, eBPF.
No license information found in the README.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.