Skip to main content
Glama

Related Servers

Alternatives to blastcheck-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to review Terraform/OpenTofu plan JSON read-only, surfacing summaries, risk-ranked changes, attribute diffs, replacement explanations, drift, and plan comparisons with secrets masked.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI to risk-review Terraform and OpenTofu plan files over MCP stdio by summarizing plans, ranking dangerous changes, diffing resources with secrets masked, and comparing two plans without running Terraform.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables state-aware Terraform/OpenTofu plan evaluation against live AWS topology and CloudWatch telemetry, detecting reliability blast radius and FinOps waste before merge.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to check npm packages, GitHub Action refs, and remote scripts before execution, returning deterministic ALLOW/DENY/REVIEW verdicts with evidence and a re-checkable manifest.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to search a security corpus, scan Terraform plan JSON for cited findings, and list sources via MCP tools grounded in CIS AWS Foundations and OWASP Top 10 CI/CD risks.
      3
      Apache 2.0

    TDQS

    A4.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: impact_emit produces a manifest from a Terraform plan, while impact_explain consumes an existing manifest and explains it. There is no overlap or possible misselection between them.

    Naming Consistency5/5

    Both tools follow the same predictable prefix-plus-verb pattern: impact_emit and impact_explain. The naming is consistent and immediately signals the shared domain and the action each tool performs.

    Tool Count3/5

    Two tools is on the thin side by the general rubric, but the server has a very narrow purpose: emit and explain impact manifests. The pair is reasonable for that scope, though it barely crosses the 'feels thin' boundary.

    Completeness5/5

    For the stated domain, the lifecycle is complete: impact_emit generates a manifest from a plan, and impact_explain supports all reasonable input paths (handle, file, or inline) and offers filtering for drill-down. There are no obvious missing operations for this focused workflow.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues