MCTS (Model Context Threat Scanner) is a local-first security scanner for MCP servers -- static and live tool discove...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 87/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if MCTS belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add mcts -- npx mctsRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove mctsNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ mcts ← registers here
MCTS (Model Context Threat Scanner) is a local-first security scanner for MCP servers -- static and live tool discovery, multiple analyzers, auditable risk scores, and JSON, SARIF, and HTML output. For authors and platform teams; CI-ready, no cloud API.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 17, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.