From mcp-tools-pro
MCP Infrastructure Scanner — cloud resources, IaC configs, CIS benchmarks, compliance rules. Use when scanning infrastructure for misconfigurations or compliance gaps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mcp-tools-pro:mcp-infra-scannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
MCP Infra Scanner is a skill designed to scan cloud infrastructures (AWS, GCP, Azure), Infrastructure as Code (IaC) configurations, and system properties over the MCP protocol. It provides resource enumeration, configuration audits, CIS benchmark compliance verification, and vulnerability scanning. It ensures that infrastructure is continuously monitored for security, compliance, and architectu...
MCP Infra Scanner is a skill designed to scan cloud infrastructures (AWS, GCP, Azure), Infrastructure as Code (IaC) configurations, and system properties over the MCP protocol. It provides resource enumeration, configuration audits, CIS benchmark compliance verification, and vulnerability scanning. It ensures that infrastructure is continuously monitored for security, compliance, and architectural best practices.
Core principle: UNSCANNED INFRASTRUCTURE IS INSECURE — INFRASTRUCTURE CHANGES MUST ALWAYS BE AUDITED.
NO INFRASTRUCTURE CHANGE CAN BE DEPLOYED TO PRODUCTION WITHOUT UNDERGOING SCANNING AND VERIFICATION. EVERY IaC CHANGE MUST PASS AT LEAST ONE SECURITY AND COMPLIANCE AUDIT.
Use this when:
Use this ESPECIALLY when:
Don't skip when:
BEFORE proceeding:
mcp-infra-scanner auth aws --profile security-audit --regions us-east-1,us-west-2,eu-west-1
mcp-infra-scanner auth gcp --service-account [email protected] --project production-project
mcp-infra-scanner auth azure --subscription prod-sub --tenant example.onmicrosoft.com
mcp-infra-scanner auth test --provider aws
BEFORE proceeding:
mcp-infra-scanner inventory list --provider aws --service ec2,s3,iam,rds
mcp-infra-scanner inventory list --provider gcp --service compute,storage,iam
mcp-infra-scanner inventory export --format json --output /tmp/inventory.json
BEFORE proceeding:
mcp-infra-scanner iac scan --path /path/to/terraform --format terraform
mcp-infra-scanner iac scan --path /path/to/cloudformation --format cloudformation
mcp-infra-scanner iac findings --scan-id scan-456 --severity critical,high
BEFORE proceeding:
mcp-infra-scanner compliance cis --benchmark "CIS AWS Foundations Benchmark v3.0.0"
mcp-infra-scanner compliance run --benchmark-id cis-aws-v3
mcp-infra-scanner compliance report --benchmark-id cis-aws-v3
BEFORE proceeding:
mcp-infra-scanner security scan --provider aws --services ec2,s3,iam
mcp-infra-scanner security network --check-public-instances
mcp-infra-scanner security encryption --check-at-rest --check-in-transit
mcp-infra-scanner security logging --check-cloudtrail --check-guardduty
Before marking complete:
If you catch yourself thinking:
ALL OF THESE MEAN: STOP. Return to the relevant phase.
Watch for these redirections:
When you see these: STOP. Return to the relevant phase.
| Excuse | Reality |
|---|---|
| "It's just a minor change, a full scan is overkill." | A single line-change in a security group can expose the entire infrastructure. Scans are mandatory. |
| "I'll write the password in the CLI statement just this once." | CLI history logs are stored persistently, leading to credential leaks. Use environment variables. |
| "CIS rules are too theoretical to apply to our startup." | Compliance frameworks provide basic baselines that protect against common infrastructure attacks. |
| "Manual checks are faster than running static scanners." | Humans miss subtle misconfigurations that automated linters catch instantly. |
| "We don't use other regions, so scanning them is a waste of time." | Attackers spin up resources in unused regions to evade detection. Scan all regions. |
After completing this process:
npx claudepluginhub haj1t/senior-dev-squad-skills --plugin mcp-tools-proGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.