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.
Valid MCP server (1 strong, 3 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.
6 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
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"
}
}
}From the project's GitHub README.
Cyntrisec Labs project. Cyntrisec's main product is EphemeralML — confidential AI inference with cryptographic receipts (AIR v1). This CLI is a standalone Labs tool. The PyPI package name
cyntrisecand MCP server IDio.github.cyntrisec/cyntrisecare stable and will not change.
[!CAUTION] Beta Software Disclaimer: This tool is currently in BETA. It is provided "as is", without warranty of any kind. While Cyntrisec is a read-only analysis tool by default, the user assumes all responsibility for any actions taken based on its findings. Always review generated remediation plans and Terraform code before application.
AWS capability graph analysis and attack path discovery.
A read-only CLI tool that:
Watch how to discover attack paths and generate fixes using natural language with Claude MCP.
+----------------------------------------------------------------------------------+
| CYNTRISEC CLI |
+----------------------------------------------------------------------------------+
| CLI Layer (Typer) |
| scan analyze cuts waste report comply can diff serve ... |
+-----------------------------+----------------------------------------------------+
| Core Engine | Storage (local) |
| - AWS collectors | ~/.cyntrisec/scans/<scan_id>/ |
| - Normalization/schema | snapshot.json, assets.json, relationships.json |
| - GraphBuilder -> AwsGraph | findings.json, attack_paths.json |
| - Path search -> paths | ~/.cyntrisec/scans/latest -> <scan_id> |
| - Min-cut + Cost (ROI) | (Windows fallback: latest is a file) |
+-----------------------------+----------------------------------------------------+
| Outputs: JSON/agent, HTML report, remediation plan + Terraform hints |
+----------------------------------------------------------------------------------+
CLI (scan) --AssumeRole--> AWS Session --Describe/Get/List--> AWS APIs (read-only)
|
v
Collectors -> normalize -> Assets + Relationships -> AwsGraph
|
v
Attack path search (BFS/DFS)
|
v
Min-cut (remediation cuts)
|
v
Cost engine (ROI)
Local artifacts: ~/.cyntrisec/scans/<scan_id>/*.json
pip install cyntrisec
If you see "cyntrisec is not recognized", the Scripts folder isn't on PATH:
# Option 1: Run with python -m
python -m cyntrisec --help
# Option 2: Add to PATH for current session
$env:PATH += ";$env:APPDATA\Python\Python311\Scripts"
Prerequisite: Ensure you have AWS CLI installed and configured with credentials (e.g.,
aws configure) or environment variables set.terraformis required for the setup step.
# 1. Create the read-only IAM role in your account
cyntrisec setup iam 123456789012 --output role.tf
# 2. Apply the Terraform
cd your-infra && terraform apply
# 3. Run a scan
cyntrisec scan --role-arn arn:aws:iam::123456789012:role/CyntrisecReadOnly
# 4. View attack paths
cyntrisec analyze paths --min-risk 0.5
# 5. Find minimal fixes (prioritized by ROI)
cyntrisec cuts --format json
# 6. Generate HTML report
cyntrisec report --output report.html
| Command | Description |
|---|---|
scan | Scan AWS infrastructure |
analyze paths | View attack paths |
analyze findings | View security findings |
analyze stats | View scan statistics |
analyze business | Business entrypoint analysis |
report | Generate HTML/JSON report |
| Command | Description |
|---|---|
setup iam | Generate IAM role Terraform |
validate-role | Validate IAM role permissions |
| Command | Description |
|---|---|
cuts | Find minimal fixes (Cost & ROI prioritized) |
waste | Find unused IAM permissions |
remediate | Generate or optionally apply Terraform plans (gated) |
| Command | Description |
|---|---|
can | Test "can X access Y?" |
diff | Compare scan snapshots |
comply | Check CIS AWS / SOC2 compliance |
| Command | Description |
|---|---|
manifest | Output machine-readable capabilities |
explain | Natural language explanations |
ask | Query scans in plain English |
serve | Run as MCP server for AI agents |
Run Cyntrisec as an MCP server for AI agent integration:
# Install with MCP support (now included by default)
pip install cyntrisec
cyntrisec serve # Start stdio server
cyntrisec serve --list-tools # List available tools
| Category | Tool | Description |
|---|---|---|
| Discovery | list_tools | List all available tools |
set_session_snapshot | Set active snapshot for session | |
get_scan_summary | Get summary of latest AWS scan | |
| Assets | get_assets | Get assets with type/name filtering |
get_relationships | Get relationships between assets | |
get_findings | Get security findings with severity filtering | |
| Attack Paths | get_attack_paths | Get attack paths with risk scores |
explain_path | Detailed hop-by-hop path breakdown | |
explain_finding | Detailed finding explanation | |
| Remediation | get_remediations | Find optimal fixes for attack paths |
get_terraform_snippet | Generate Terraform code for remediation | |
| Access | check_access | Test if principal can access resource |
get_unused_permissions | Find unused IAM permissions | |
| Compliance | check_compliance | Check CIS AWS or SOC 2 compliance |
compare_scans | Compare scan snapshots |
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"cyntrisec": {
"command": "python",
"args": ["-m", "cyntrisec", "serve"]
}
}
}
Run the following command to configure the server:
claude mcp add cyntrisec -- python -m cyntrisec serve
Locate your agent configuration (e.g., ~/.gemini/antigravity/mcp_config.json) and add:
{
"mcpServers": {
"cyntrisec": {
"command": "python",
"args": ["-m", "cyntrisec", "serve"]
}
}
}
This tool makes read-only API calls to your AWS account. The IAM role
should have only Describe*, Get*, List* permissions.
All data stays on your local machine. Nothing is sent to external servers.
Scan results are stored in ~/.cyntrisec/scans/.
By default, Cyntrisec is read-only and does not modify your AWS infrastructure.
Cyntrisec includes an explicitly gated path that can execute Terraform only if you intentionally enable it.
This mode is:
--enable-unsafe-write-mode--execute-terraform) to run TerraformIf you do not pass these flags, Cyntrisec will never run terraform apply.
Cyntrisec makes no AWS write API calls during scanning and analysis.
The only supported "write" behavior is optional execution of Terraform locally on your machine, and only when explicitly enabled via unsafe flags.
Every AWS API call is logged in CloudTrail under session name cyntrisec-cli.
Cyntrisec runs with a read-only IAM role. Generate the recommended policy with
cyntrisec setup iam <ACCOUNT_ID> and keep permissions to Describe*, Get*,
and List*. Live modes (waste --live, can --live) require extra IAM
permissions; the generated policy and docs cover those additions.
Primary output is JSON to stdout. When stdout is not a TTY, the CLI automatically switches to JSON:
cyntrisec analyze paths --format json | jq '.paths[] | select(.risk_score > 0.7)'
Agent-friendly output wraps results in a structured envelope:
cyntrisec analyze paths --format agent
{
"schema_version": "1.0",
"status": "success",
"data": {...},
"artifact_paths": {...},
"suggested_actions": [...]
}
| Code | Meaning |
|---|---|
| 0 | Success / compliant |
| 1 | Findings / regressions / denied |
| 2 | Usage error |
| 3 | Transient error (retry) |
| 4 | Internal error |
Use in CI/CD:
cyntrisec scan --role-arn $ROLE_ARN || exit 1
cyntrisec diff || echo "Regressions detected"
Scan results are stored locally:
~/.cyntrisec/
|-- scans/
| |-- 2026-01-17_123456_123456789012/
| | |-- snapshot.json
| | |-- assets.json
| | |-- relationships.json
| | |-- findings.json
| | `-- attack_paths.json
| `-- latest -> 2026-01-17_...
`-- config.yaml
This project follows Semantic Versioning. See CHANGELOG.md for release notes.
Apache-2.0
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.