Skip to main content
Glama
h4cd0c

Stratos

by h4cd0c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Stratos

No user-submitted related servers found.

    Related Servers

    • pentest-mcp-server

      Dr-yato
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables authorized penetration testing and security assessments with CVE monitoring, vulnerability scanning, and reporting features.
      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

    • MCP Shamash

      NeoTecDigital
      F
      license
      B
      quality
      D
      maintenance
      Enables security auditing, penetration testing, and compliance validation with tools like Semgrep, Trivy, Gitleaks, and OWASP ZAP. Features strict project boundary enforcement and supports OWASP, CIS, and NIST compliance frameworks.
      7
      -

    • Azure Security MCP Agent

      chouaieb161
      F
      license
      Not graded
      quality
      D
      maintenance
      An AI-powered security agent that utilizes MCP tools and Groq LLMs to analyze Azure infrastructure, audit security groups, and identify storage misconfigurations. It enables users to perform natural language security assessments and ensure compliance with CIS Azure best practices.
      -
    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.5/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting specific Azure resources or security aspects. Minor overlap exists between tools like azure_analyze_nsg_rules and azure_analyze_firewall_policies, but descriptions clarify the differences.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case with the 'azure_' prefix (e.g., azure_analyze_app_service_security, azure_enumerate_subscriptions). No mixing of styles.

    Tool Count3/5

    With 43 tools, the set is on the high side but justified for a comprehensive Azure security toolkit. The count borders on heavy, but each tool targets a specific service or attack vector, making it reasonable.

    Completeness4/5

    The tool surface covers a broad range of Azure services and security aspects including networking, compute, storage, databases, identity, containers, and policies. Minor gaps exist, such as limited coverage for Azure Active Directory beyond service principals.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources