Skip to main content
Glama
aos-standard

mcp-blast-radius

by aos-standard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-blast-radius

No user-submitted related servers found.

    Related Servers

    • mcpaudit

      AndrewXuTurtle
      A
      license
      Not graded
      quality
      C
      maintenance
      Audits MCP server configurations and packages for security risks such as typosquats, credential exposure, and malicious code, with zero dependencies and no execution.
      2
      MIT
    • dr-mcp by Inferensys

      dr-mcpofficial

      Inferensys
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first MCP audit and cleanup tool that scans MCP configs to find stale servers, abandoned packages, duplicates, context-heavy tools, risky permissions, and major upgrades, generating reversible patch plans.
      89
      MIT

    • gke-cred-audit

      rrupesh
      A
      license
      Not graded
      quality
      D
      maintenance
      Defensive credential-exposure auditor for GKE that inventories workload identity, service account tokens, and RBAC posture, exposing findings via an MCP server at /mcp.
      Apache 2.0

    • mcp-heimdall

      caglarbozkurt
      A
      license
      Not graded
      quality
      A
      maintenance
      Security scanner for MCP servers — vet an MCP before you wire it into an agent. Detects prompt-injection, credential exfiltration (via taint analysis), RCE, and supply-chain risks, and catches cross-server exfil chains no single server reveals. Zero-dependency local CLI, SARIF output, CI-gateable, no account.
      65
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clear distinct purposes: one checks connectivity (self-test) and the other validates agent directories. No overlap in functionality.

    Naming Consistency5/5

    Both tools use the consistent prefix 'aos_compliance_' followed by a verb in snake_case, creating a predictable naming pattern.

    Tool Count3/5

    With only 2 tools, the surface feels thin for a compliance validation server. However, it may be acceptable if the domain is narrow.

    Completeness2/5

    The server lacks common operations such as listing directories, retrieving past validations, or managing configurations, making it incomplete for typical compliance workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources