iac-copilot
Related Servers
Alternatives to iac-copilot
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceExposes seven MCP tools that let an AI coding agent detect a project's stack, fetch the priority security checks for that platform, search 2,057 OWASP-derived check cards with file-and-commit provenance, and record evidence-backed pass/fail results in a report.7MIT
- AlicenseBqualityCmaintenanceGives AI coding agents on-demand security playbooks, a code scanner they can run on their own output, and live lookups against CISA KEV, NVD and OSV so they verify threats instead of guessing. Runs locally with no API keys or accounts, exposing skills, tools and a secure-build prompt to Claude Code, Codex, Cursor or any MCP client.13Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.103 npmMIT

ZeroPath MCP Serverofficial
AlicenseBqualityCmaintenanceAllows developers to query security findings (SAST issues, secrets, patches) using natural language within AI-assisted tools like Claude Desktop, Cursor, and other MCP-compatible environments.1710MIT- AlicenseAqualityAmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.1598 npm15Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents to run deterministic, fully local static security and compliance audits of code, configurations, and dependencies through 32 MCP tools covering 24 vulnerability categories. It also detects the project stack, generates risk reports and checklists, suggests stack-aware remediations, and re-validates fixes to confirm vulnerabilities were eliminated.321MIT
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: searching the guidance corpus, scanning a Terraform plan, and inspecting corpus sources. There is no overlap or ambiguity between them.
All tool names follow the same snake_case verb_noun pattern: search_corpus, scan_terraform_plan, list_sources. This is consistent and predictable.
Three tools is on the lower end but still within the well-scoped range. Each tool earns its place for the server's focused IaC copilot purpose.
The core workflow of searching guidance, scanning a plan, and verifying corpus sources is covered. Minor gaps exist such as no direct tool for retrieving a full document or listing supported scan rules, but these are not major dead ends.