Skip to main content
Glama
ASCIT31

@darkmoon_ai/mcp-server

by ASCIT31
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @darkmoon_ai/mcp-server

No user-submitted related servers found.

    Related Servers

    • keel

      lutfizp
      A
      license
      C
      quality
      B
      maintenance
      Enables authorized pentest and bug bounty workflows from any MCP client, with scoped recon, per-host rate limits, and scanner output turned into deduplicated, triaged finding cards.
      9
      32 PyPI
      1
      MIT

    • Cockpit Lite MCP Server

      kom9
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized penetration testing through MCP, providing parallel reconnaissance, vulnerability scanning, attack path analysis, and self-contained HTML reporting with compliance tagging.
      MIT

    • pentest-ai

      0xSteph
      A
      license
      Not graded
      quality
      A
      maintenance
      Autonomous pentests from one command: real security tools, working PoCs, and audit-ready reports, all driven via MCP.
      271 PyPI
      1,709
      MIT

    • apex

      nadirzhon
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables authorized bug bounty automation via a scope-enforced MCP bridge, supporting web, secrets, mobile, and LLM red-team scanning, with reporting and advisory.
      MIT

    • pyntra

      prnvv2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to orchestrate 100+ security tools over MCP for authorized penetration testing, including recon, scanning, exploitation, attack-chain planning, and knowledge-base retrieval.
      5
      Apache 2.0
    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

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct action (start, status, list campaigns, get findings), but the relationship between a 'run' and a 'campaign' is not fully clear, which could cause slight misselection between get_run_status and list_campaigns when checking progress.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (run_pentest, get_run_status, list_campaigns, get_findings), with clear verb prefixes that are easy to predict.

    Tool Count5/5

    Four tools is well-scoped for a focused pentest service; each tool (start, monitor, list campaigns, read findings) earns its place without redundancy or bloat.

    Completeness3/5

    Core start-monitor-results workflow is covered, but notable gaps exist: no cancel/stop for long-running runs, and no explicit way to map a run_id to its resulting campaign, forcing agents to guess from list_campaigns.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources