In-depth architectural comparison of the Agentforge Trust MCP and Sast 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
Agentforge Trust MCP
Security · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Sast MCP Server
Security · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Agentforge Trust MCP if you need specialized Security tools running via a local process. Choose Sast 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 Agentforge Trust MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Query the AgentForge Trust Score (0-100 across five dimensions: security, code health, behavioral audit, community trust, EU compliance) for any MCP server before connecting. Exposes checktrust, evaluatepolicy, listtrusted, and recommend tools. 3,600+ servers audited, free public API.
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).
Category & Scope
Tools & Capabilities Breakdown
Agentforge Trust MCP Tools (8)
check_trust
Fetch the AgentForge Trust Score for an MCP server. Returns the overall score (0-100), per-dimension breakdown (code_health, security_scan, behavioral_audit, community_trust, eu_compliance), and badges. Use before connecting to any MCP server.
evaluate_policy
Check whether a server passes a trust policy. Returns allowed:true/false plus individual check results. Example policy: {min_overall: 70, required_badges: ['actively_maintained']}. Use this to gate agent decisions like 'should I use this server for financial data?'.
list_trusted
Search AgentForge catalog for servers matching a category and minimum trust threshold. Returns up to 25 results sorted by trust score.
recommend
Given a natural-language use case, recommend MCP servers filtered by trust. Example: 'I need to validate Czech VAT IDs and convert ISDOC invoices'. Uses AgentForge semantic search + trust filter.
discover
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).
Agentforge Trust MCP is categorized under Security and uses a local stdio subprocess. In contrast, Sast MCP Server belongs to Security using local stdio subprocess. Select Agentforge Trust MCP when you need capabilities focused on security and Sast MCP Server when you require tools for security.
Browse the AgentForge catalog of MCP servers. Supports full-text search, semantic search, and category filtering. No authentication required. Use this when you need to find servers offering a specific capability (e.g. 'GitHub PR automation', 'EU VAT validation'). Returns server metadata, tool counts, pricing tier, and trust scores. Each result carries TWO trust fields: `audit_score` (0-100, dynamic from the AgentForge audit pipeline — AUTHORITATIVE for policy gating, may be null if not yet audited) and `trust_score` (0-10, legacy community rating — for display fallback only). Always prefer audit_score when present; treat null audit_score as 'audit pending'.
broadcast_search
Search ACROSS multiple MCP servers in a single call. Returns relevant tools per server, sorted by relevance. Replaces N sequential discover+capabilities calls. Requires AGENTFORGE_API_KEY (set in env or call register_agent first). Use this when an agent needs to fan out a query like 'find me anything that can parse DICOM medical images' across the catalog.
call_tool
Invoke any tool on any MCP server in the AgentForge catalog. AgentForge proxies the call, applies rate limits, billing (per-call or wallet credits), and returns the result. Requires AGENTFORGE_API_KEY. Use this to actually USE a server's capability after discovery, e.g. call_tool(server='github-pro', tool='create_pr', input={...}).
register_agent
Self-register this agent with AgentForge. Returns an af_agent_* API key that unlocks broadcast_search and call_tool. Run once at agent startup, store the key in env as AGENTFORGE_API_KEY. No auth required for registration. Idempotent on slug — running twice produces a uniqued slug.
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.
scan_git_history
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.