Skip to main content
Glama
uziii2208

mcp2agy

by uziii2208
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp2agy

No user-submitted related servers found.

    Related Servers

    • SecPipe by FuzzingLabs

      SecPipeofficial

      FuzzingLabs
      F
      license
      A
      quality
      F
      maintenance
      Enables AI agents to orchestrate security research workflows by connecting to containerized security tools via MCP, allowing automated vulnerability analysis and pipeline execution.
      24
      803
      -

    • antigravity

      Snake76500
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local AI agents to generate code and interact with Google Antigravity (Gemini Pro) via MCP, consuming zero API tokens.
      -

    • code-audit-mcp

      kkk1259
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables automated security code auditing using LLM and MCP, including AST parsing, taint analysis, dataflow tracing, and automated PoC generation for multi-language codebases.
      1
      MIT

    • zeroforge

      mika8313
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables adaptive binary 0day research with persistent knowledge graph and adaptive planning, automating vulnerability analysis and exploit development through HexStrike and local tools via MCP.
      -

    • Decepticon

      itsdanylol
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous bug bounty hunting with H1 auto-submit, profit tracking, and a live dashboard. Coordinates real-time state, credential vault, session management, and payload generation for MCP-compatible AI agents.
      4 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes (e.g., calculate_cvss vs generate_poc), but scan_file and analyze_code both scan for vulnerabilities with overlapping output structures, and check_reachability is a subset of verify_finding's workflow. Descriptions help differentiate, but some confusion is possible.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (generate_fix, scan_file, verify_finding, audit_pipeline). No mixed conventions or vague verbs; naming is highly predictable.

    Tool Count5/5

    With 15 tools, the server is well-scoped for a comprehensive security audit pipeline. Each tool addresses a distinct stage (profiling, scanning, verification, fixing, reporting, chaining), and none feel redundant or excessive.

    Completeness5/5

    The tool surface covers the full audit lifecycle: profile_target (discovery), scan_file/analyze_code (detection), verify_finding/check_reachability (validation), calculate_cvss (scoring), generate_poc (exploitation), generate_fix/check_fix_completeness (remediation), chain_findings (synthesis), and generate_report (output). The audit_pipeline orchestrates everything, leaving no major dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources