cloud-pathfinder
Related Servers
Alternatives to cloud-pathfinder
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for auditing AI agent permissions and access by scanning for the trifecta of credentials, injection, and reach without heavy infrastructure.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for automated AWS security scanning. It detects over-privileged IAM roles and S3 Public Access Block misconfigurations, enabling least-privilege enforcement through tools like list_iam_roles, analyze_iam_policy, and analyze_s3_security.MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that parses Terraform .tfstate files and lets AI agents audit enterprise infrastructure for security misconfigurations without requiring direct cloud credentials.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that provides an execution graph of AWS services, enabling agents to query API contracts, generate least-privilege IAM policies, and register traps.-
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables security auditing for MCP configurations and AI agents, including prompt injection testing, data flow tracing, and security policy generation.16 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables LLMs to query and reason over Active Directory attack graphs collected by BloodHound, providing attack paths, blast radius analysis, choke points, and defender remediation advice.MIT
TDQS
Scored across 2 tools
Each tool targets a distinct task: audit_iac_attack_paths performs a single-state static scan, while diff_attack_paths analyzes changes between two states. Their descriptions clearly separate use cases (pre-apply/PR vs. CI/CD gate), leaving no ambiguity.
Both tool names follow the verb_noun pattern (audit_attack_paths, diff_attack_paths) with a consistent suffix. The inclusion of 'iac' in one name is a minor, non-disruptive variation that still aligns with the overall naming scheme.
With only two tools, the set feels minimal, but each tool is essential and non-redundant for the server's narrow purpose of IaC attack-path analysis. The count is at the borderline of what is considered appropriate.
The two tools cover the complete lifecycle: a static snapshot audit and a differential change analysis. No obvious gaps exist, as both core operations for the domain are represented and no dead ends are apparent.