Skip to main content
MCP Servers / ThreatCorralling

ThreatCorralling

Contributed

Correlates results from Checkmarx with Tenable WAS via a JSON glue file.

Authorgiraldomauricio
Transportstdio
Runtimepython
LicenseMIT
AddedAug 5, 2026

Compatible Clients

Claude DesktopClaude Code

Integrations

TenableCheckmarx OneSecurityScorecard

Tools (6)

  1. get_checkmarx_sast_for_scoped_projects

    Get Checkmarx Projects selected from the JSON.

  2. get_tenable_was_for_scoped_domains

    Get Tenable WAS results selected from the JSON.

  3. get_compliance_mapping

    Matched Compliance metrics with the results from the correlation

  4. get_approved_remediation_pattern

    Suggest remediation patterns where the code or the finding allows it based in the correlations

  5. generate_regression_test_template

    Suggest regression tests that can be shared with developers to proff the code against the finding.

  6. get_security_scorecard_findings

    Gets data from Security Scorecard to add to TenableWAS findings.

Tags

CheckmarxSASTWASTenableCxOne

ThreatCorraling connects CheckmarxOne vulnerabilities (SAST, SCA, KICS) with results from TenableWAS (Formerly Ermetic) for a deep analysis of the risk from Left (Code) to Right (Deployment)

What it does

ThreatCorralling is an intelligent, extensible Vulnerability Correlation Agent and Model Context Protocol (MCP) server. It bridges the gap between disparate security tools by analyzing scoped assets across platforms like Checkmarx SAST and Tenable WAS.

How it works

Using FastMCP wrapper, the file sits in the background and waits for an external AI to ask for a correlation between CxOne Projets and Tenable WAS targets. It then executes the tools locally and passes the data back to the AI. For performance, the server caches the results for further use. This feature can be replaced by a database or any other better persistence method.