MCP.Market

Cyntrisec CLI (Historical) MCP server

by cyntrisec·io.github.cyntrisec/cyntrisec·v0.1.14·4 stars
No reviews yet

Historical AWS analysis CLI; not a current Cyntrisec product.

B71/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B71/100

full report

Adoption
New

4 stars55 downloads/wk

Reviews

Write one

Nobody has reviewed Cyntrisec CLI (Historical) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cyntrisec CLI (Historical) tools (15)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_access

    Test if a principal can access a resource.

  • check_compliance

    Check compliance against CIS AWS or SOC 2 framework.

  • compare_scans

    Compare latest scan to previous scan.

  • explain_finding

    Get detailed explanation of a security finding.

  • explain_path

    Get detailed explanation of an attack path.

  • get_assets

    Get assets from the scan with optional filtering.

  • get_attack_paths

    Get discovered attack paths from the latest scan.

  • get_findings

    Get security findings from the scan.

  • get_relationships

    Get relationships between assets with optional filtering.

  • get_remediations

    Find optimal remediations that block attack paths.

  • get_scan_summary

    Get summary of the latest AWS scan.

  • get_terraform_snippet

    Get Terraform code snippet for a specific remediation.

  • get_unused_permissions

    Find unused IAM permissions (blast radius reduction opportunities).

  • list_tools

    List all available Cyntrisec tools.

  • set_session_snapshot

    Set or retrieve the active snapshot id used for subsequent calls.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan60 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 144 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cyntrisec CLI (Historical) compares

Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 43% of 2,174 E-commerce servers
Tools
15
the typical E-commerce server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
4
more than 86% of 1,047 E-commerce servers
Downloads a week
55
more than 52% of 411 E-commerce servers with a package

What its tools let an agent do: 14 read · 1 change

Install Cyntrisec CLI (Historical) in Claude Code, Cursor or VS Code

claude mcp add cyntrisec -- uvx cyntrisec
Add to Cursor

What the publisher says

From the Cyntrisec CLI (Historical) repository's README, as published. We do not edit it. Read it on GitHub

Cyntrisec CLI

<!-- mcp-name: io.github.cyntrisec/cyntrisec -->

Historical pre-company project. cyntrisec-cli was created before Cyntrisec narrowed its company focus to EphemeralML and AIR v1. It is not a current Cyntrisec product, support surface, or commercial offering. The PyPI package name cyntrisec, CLI command cyntrisec, and MCP server ID io.github.cyntrisec/cyntrisec are retained only to avoid breaking historical installs.

[!CAUTION]

Historical Software Disclaimer: This tool is no longer an active Cyntrisec product. It is provided "as is", without warranty of any kind.

While the CLI 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.

Historical AWS capability graph analysis and attack path discovery CLI.

A read-only CLI tool that historically:

  • Scans AWS infrastructure via AssumeRole
  • Builds a capability graph (IAM, network, dependencies)
  • Discovers attack paths from internet to sensitive targets
  • Prioritizes fixes by ROI (security impact + cost savings)
  • Identifies unused capabilities (blast radius reduction)
  • Outputs deterministic JSON with proof chains

Demo

Watch how to discover attack paths and generate fixes using natural language with Claude MCP.

Architecture

+----------------------------------------------------------------------------------+
|                                   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              |

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cyntrisec CLI (Historical): common questions

Is Cyntrisec CLI (Historical) MCP server safe?
Mostly: it is graded B (71/100). Read the Cyntrisec CLI (Historical) safety report
How do I install Cyntrisec CLI (Historical)?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cyntrisec CLI (Historical) need an API key?
Yes. The registry entry asks for AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY.
Is Cyntrisec CLI (Historical) maintained?
The last commit was 182 days ago (2026-05-06). The latest release is v0.1.14.
What can I use instead of Cyntrisec CLI (Historical)?
Servers from other publishers that do the same job: Loki Mode MCP server, PostHog MCP Server and New-Term Radar MCP server.
How does Cyntrisec CLI (Historical) compare with other E-commerce MCP servers?
safety score 71/100 (higher than 43% of 2,174 E-commerce servers); tools 15 (the typical E-commerce server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Cyntrisec CLI (Historical)

Same job from other publishers: the closest match first, then the best rated.

  • Loki Mode
    Autonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.
    B
  • PostHog MCP Server
    Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
    A
  • New-Term Radar
    New AI model, product and repo names as they surface, and the search terms behind them, sized.
    B
  • Idea Reality
    Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
    B
  • Stripe
    MCP server integrating with Stripe - tools for customers, products, payments, and more.
    A