AFL++ MCP server
Related Servers
Alternatives to AFL++ MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to operate ARL, ScopeSentry, and XingRin attack surface management platforms through stdio tools for listing resources, testing connections, creating/managing tasks, and retrieving assets.Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables authorized penetration testers to run reconnaissance, web fuzzing, vulnerability scanning, brute-force/password cracking, traffic capture, privilege-escalation audits, wordlist generation, and client-report workflows over stdio, HTTP, or SSE with optional bearer/OIDC authentication.298 npmGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure AI Foundry services through a unified interface for model exploration and deployment, knowledge indexing and search, AI evaluation, and fine-tuning operations. Supports both GitHub token-based model testing and full Azure deployment workflows.3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables stateful binary analysis and pwn research through GDB/pwndbg debugging capabilities. Supports loading binaries, setting breakpoints, memory analysis, compilation with sanitizers, and process management for vulnerability research.-
- AlicenseNot gradedqualityAmaintenanceEnables professional penetration testers to run authorized reconnaissance, scanning, exploitation, and reporting workflows through MCP tools such as nmap, ffuf, nuclei, hashcat, and report generation, with STDIO/HTTP/SSE transport and bearer/OIDC auth support.298 npmGPL 3.0
- AlicenseBqualityCmaintenanceEnables interaction with the AssemblyLine 4 malware analysis platform, allowing file submissions, URL analysis, and search capabilities via natural language.20MIT
TDQS
Scored across 30 tools
Most tools have clear, distinct purposes. Minor overlap exists between status, whatsup, and campaign_summary, which all report on fuzzing progress, and among crash-related tools (repro_crash, crash_report, casr_report), but descriptions provide enough distinction.
The majority follow a verb_noun pattern with underscores (init_workspace, start_fuzz, list_findings). A few exceptions like whatsup and showmap break the pattern, and casr_report uses an abbreviation, but the overall convention is consistent.
At 30 tools, the set exceeds the 25-tool threshold for 'too many'. While the AFL++ domain is complex, several meta tools (help, version, list_tools) and overlapping status/report functions could be consolidated, making the count feel heavy.
The tool set covers the core fuzzing lifecycle: workspace setup, building, corpus management, execution, monitoring, and crash analysis. A notable gap is the lack of a 'list running jobs' tool, but most workflows are supported end-to-end.