Skip to main content
Glama
KanenasCS

Azure NeuroMap MCP

by KanenasCS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Azure NeuroMap MCP

No user-submitted related servers found.

    Related Servers

    • AWS MCP Audit

      oldcoder01
      F
      license
      D
      quality
      D
      maintenance
      Enables read-only assessment of AWS environments by inventorying resources, running security and operational checks, and generating actionable reports with cost analysis. Designed for contractors with support for assume-role authentication using external IDs.
      10
      -

    • aws-audit-mcp

      OmniNomadLLC
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to run read-only AWS security audits and receive normalized, severity-ranked findings about account posture, such as stale access keys, missing MFA, public buckets, open security groups, and CloudTrail coverage.
      11
      MIT

    • Stratos

      h4cd0c
      A
      license
      A
      quality
      C
      maintenance
      Enterprise-grade Azure security assessment toolkit with multi-location scanning, IMDS exploitation, attack path analysis, and compliance reporting. Enables authorized penetration testing and compliance audits across all Azure regions.
      43
      11 npm
      MIT

    • AWS Cost Saver

      prajapatimehul
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables scanning AWS accounts for cost optimization opportunities by reading resource configurations and pricing data, without making any modifications.
      22
      MIT
    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

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have distinct scopes (find/get, scan/summary/export, per-resource vs estate-wide searches). A few pairs overlap conceptually—nsg_rules_for vs search_nsg_rules, firewall_rules vs search_firewall_rules, and who_has_access vs identity_permissions—but descriptions clarify per-resource vs global/bulk and RBAC vs managed-identity scopes.

    Naming Consistency4/5

    All names use lowercase snake_case consistently, which is the dominant pattern. Minor deviations exist: some are verb-first (scan_infrastructure, find_resource, get_node), others noun-first (infra_summary, firewall_rules, ingress_paths), and who_has_access is a question phrase, but the set remains readable and predictable.

    Tool Count4/5

    16 tools is slightly above the ideal 3–15 range but still well-scoped for a comprehensive Azure network graph and security analysis server. Each tool appears to cover a distinct analysis need, with no obvious filler.

    Completeness4/5

    The surface covers scanning, resource lookup, NSG/firewall rule analysis, routes, hybrid connectivity, RBAC/identity permissions, access verdicts, public exposure, and map export—strong coverage for read-only infrastructure analysis. Minor gaps like snapshot comparison or private DNS zone specifics are not fatal but leave some adjacent lifecycle concerns uncovered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources