FuzzingLabs/mcp-security-hub

Holds the engagement record an agent loses when its context fills: the scope, which methodology phases have been covered, and findings with the evidence behind them. The agent tests; this remembers.

Keeps the tool surface deliberately small, a handful of composite calls plus reference material the model loads only when it needs it, and ships a system prompt with rules about what the graph does and does not prove. Reaches Entra as well as on-premises.

Serves a large tool catalogue over MCP and adds a layer of its own that picks which tool to run and with what flags, so the client's model chooses the goal rather than the command line.

One MCP server per security tool, each a thin wrapper over that binary's flags. Development has moved to a successor project under a different name.

A thin bridge giving a model a shell on a Linux box you already run, plus a short list of named tool wrappers. Raw command execution is the point; the wrappers are convenience.

Drives Metasploit over its RPC interface: search the modules, run an exploit or a post module, generate a payload, and send commands into a session that is already open.

Turns BloodHound's own Cypher query library into one MCP tool per query, so you ask for an attack path in English and the server runs a query someone already wrote and tested.

Reads a running ROADrecon instance so a model can question the Entra tenant it already collected, with prompt templates for the analyses people usually run over that data.

One hardened container per tool, brought up with Compose, so a job runs only the servers it needs instead of one process holding everything.