Scan complete
Your security snapshot
Issues found
Security problems MCTS flagged — fix Critical and High first.
| Severity | Count | What it means |
|---|---|---|
| Total | 0 |
Security Score
0–100 points · higher is better · not a percentage
Grade —
—
Overall risk level
Multi-factor score — higher number means more danger
—
What drives the risk?
Each spoke shows which risk factor weighs most on this scan. 100 = dominant factor.
What to do next
Start with urgent issues, then follow the recommended fixes below.
Fix these first
Highest-severity findings from this scan.
What already looks good
Checks that ran cleanly — click any row for details.
Summary & recommended actions
What this means
Top fixes (P1 first)
Risk breakdown
Which findings and categories add the most to your overall risk score.
Biggest risk contributors
Findings that added the most to your absolute risk number.
| Finding | Tool | Risk added | Why |
|---|
Category health
100 = no problems in that OWASP bucket · lower = more findings there.
Scan coverage
How many security checks ran, and how they grouped into risk areas.
Area scores (legacy)
Points out of 100 per security area — separate from the main risk score above.
Trends & benchmarks
Track changes across scans and see where your score sits on the scale.
Risk by category
How each security area compares to industry benchmarks.
Score over time
Run multiple scans from the same folder to compare.
No scan history yet
Run mcts scan at least twice from the same project folder. History is stored in mcts_analysis/history.json.
Risk level guide
Where your current score falls on the scale.
How to read this report
Understanding the numbers
Like a health rating: 100 = best, 0 = worst. Not a percentage and not “% of tests passed.”
Issues, severity rows, checks run, and tools discovered are totals — how many items MCTS counted.
Sums risk from eight security factors on tool findings. Higher = worse — opposite direction from the 0–100 benchmark score.
Issues to Fix
Every security problem MCTS found, sorted by severity. Fix Critical and High items first.
| Severity | Finding | Location | Technique | CWE | Category | OWASP | Affected Tool | Confidence | Remediation |
|---|
MCTS-T Technique Map
Regression technique coverage for this scan.
Tool Capability Matrix
Inferred capability flags per discovered MCP tool.
All Security Checks
Every analyzer MCTS ran — expand any card to see what it checked, OWASP mapping, and techniques.
Passed Checks
Passed = no pattern matches in this scan scope. Expand a card to see what was inspected and framework coverage.
Checks With Findings
Attack Paths
How tools could be chained together for a multi-step attack (read → exfiltrate, etc.).
Each arrow shows a possible step between tools.
OWASP Mapping
How findings map to OWASP LLM and MCP Top 10 categories.
OWASP LLM Top 10
Industry-standard categories for LLM application security.
OWASP MCP Top 10
MCP-specific risk categories — gaps mirror compliance meta-findings when analyzers did not cover a category.
How to Fix
Prioritized remediation steps — P1 is most urgent.
Raw Data
Full machine-readable scan JSON for automation and debugging.