Server data from the Official MCP Registry
AWS security analysis: attack paths, compliance checking, and remediation planning.
AWS security analysis: attack paths, compliance checking, and remediation planning.
Set these up before or after installing:
Environment variable: AWS_PROFILE
Environment variable: AWS_DEFAULT_REGION
Environment variable: AWS_ACCESS_KEY_ID
Environment variable: AWS_SECRET_ACCESS_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cyntrisec-cyntrisec": {
"env": {
"AWS_PROFILE": "your-aws-profile-here",
"AWS_ACCESS_KEY_ID": "your-aws-access-key-id-here",
"AWS_DEFAULT_REGION": "your-aws-default-region-here",
"AWS_SECRET_ACCESS_KEY": "your-aws-secret-access-key-here"
},
"args": [
"cyntrisec"
],
"command": "uvx"
}
}
}Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
Scanned 4 files · 1 finding
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Be the first to review this server!