Skip to main content
Glama

Related Servers

Alternatives to AFL++ MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      3
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables interaction with the AssemblyLine 4 malware analysis platform, allowing file submissions, URL analysis, and search capabilities via natural language.
      20
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to manage workspaces, load and run recon modules, install marketplace modules, and query reconnaissance data, exposing the full recon-ng OSINT framework.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to compile, debug, sample, and inspect MCU firmware through J-Link/pyOCD or a mock engine, including breakpoints, watchpoints, single-stepping, register access, and flash dump operations.
      MIT

    TDQS

    C2.9/5.0

    Scored across 30 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues