blastcheck-mcp
Related Servers
Alternatives to blastcheck-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables AI coding agents to plan, policy-check, and cost-estimate Terraform changes while requiring human approval through Slack or CLI before any terraform apply can execute.97 npmMIT
- AlicenseAqualityCmaintenanceEnables 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.3Apache 2.0
TDQS
Scored across 2 tools
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.
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.
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.
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.