Sast MCP Server vs MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sast MCP Server vs MCP Server
In-depth architectural comparison of the Sast MCP Server and MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Sast MCP Server
Security · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
MCP Server
Security · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Verdict Summary: Choose Sast MCP Server if you need specialized Security tools running via a local process. Choose MCP Server if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Sast MCP Server when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: DEFECTDOJO_URL, GITHUB_TOKEN, JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN.
SAST/DAST server exposing 11 security scanners (Bandit, Semgrep, Trivy, CodeQL, Checkov, Gitleaks, OSV-Scanner, Grype, OWASP ZAP, and more) with closed-loop remediation (scan→patch→re-scan→verify), SARIF/SBOM/VEX export, compliance reporting, and CI integrations (GitHub Advanced Security, DefectDojo, Slack, Jira).
MCP server for RAD Security, providing AI-powered security insights for Kubernetes and cloud environments. This server provides tools for querying the Rad Security API and retrieving security findings, reports, runtime data and many more.
Category & Scope
Tools & Capabilities Breakdown
Sast MCP Server Tools (27)
scan_vulnerabilities
Scan a target directory for security vulnerabilities using a SAST tool.
ignore_vulnerability
Ignore a specific vulnerability finding so it won't appear in future scans.
unignore_vulnerability
Remove a vulnerability from the ignore list so it appears in future scans again.
list_scanners
List all available SAST scanners, their status, and supported languages.
Returns information about each scanner including whether it is installed
and ready to use, what languages it supports, and how to install it.
list_ignored_vulnerabilities
List all currently ignored vulnerability findings for a project.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Sast MCP Server is categorized under Security and uses a local stdio subprocess. In contrast, MCP Server belongs to Security using local stdio subprocess. Select Sast MCP Server when you need capabilities focused on security and MCP Server when you require tools for security.
Scan the entire git history for leaked secrets and credentials using Gitleaks.
Traditional SAST only scans the current state of files. This tool deeply
analyzes the `.git` directory to find API keys, passwords, and tokens
that were committed in the past but may still be valid.
run_active_scan
Run an active dynamic scan (DAST) using OWASP ZAP.
Unlike SAST which only looks at code, this orchestrates spinning up the
application via Docker Compose, waiting for it to be ready, and then
running a ZAP dynamic baseline scan against the running instance.
export_sarif
Run a SAST scan and export results in SARIF 2.1.0 format for CI/CD integration.
SARIF is the industry standard format consumed by GitHub Code Scanning,
GitLab SAST, Azure DevOps, and other CI/CD platforms.
scan_all
Scan with ALL installed scanners in parallel, returning deduplicated results.
Automatically detects which scanners are installed, runs them concurrently,
and deduplicates findings across scanners using content-based hashing.
This is the recommended tool for comprehensive security scanning.
scan_image
Scan a container image for vulnerabilities and secrets.
Pulls and analyzes a container image reference (e.g. `nginx:1.25`,
`ghcr.io/org/app@sha256:...`) with Trivy or Grype, returning the same
normalized findings as a source scan.
save_baseline
Run a scan and save the results as a named baseline for future comparison.
compare_baseline
Compare current scan results against a saved baseline.
Shows new vulnerabilities, fixed vulnerabilities, and severity trends.
+15 more tools listed on main page
MCP Server Tools (54)
list_containers
List containers secured by RAD Security with optional filtering by image name, image digest, namespace, cluster_id, or free text search
get_container_details
Get detailed information about a container secured by RAD Security
list_clusters
List Kubernetes clusters managed by RAD Security
get_cluster_details
Get detailed information about a specific Kubernetes cluster managed by RAD Security
who_shelled_into_pod
Get k8s audit logs with information about users who shelled into a pod
list_images
List container images with optional filtering by page, page size, sort, and search query
list_image_vulnerabilities
List vulnerabilities in a container image with optional filtering by severity
get_top_vulnerable_images
Get the most vulnerable images from your account
get_image_sbom
Get the SBOM of a container image
ignore_cve
Ignore a CVE for this account so it no longer appears in vulnerability reporting. Use for confirmed false positives, accepted risks, or won't-fix decisions. Do NOT use for remediated CVEs — those drop off automatically on the next scan.
unignore_cve
Remove an account-wide CVE disposition, restoring the CVE to vulnerability reporting.
list_cve_dispositions
List active CVE dispositions (ignored / false positive) for this account, with reason and author.