ARGUS
Enables AI agents to perform comprehensive, zero-infrastructure codebase analysis through 24 MCP tools, covering security, quality, architecture, type safety, git history, and dead code detection with high precision and local privacy.
README
ARGUS
Autonomous Repository Guardian and Unified Scanner
"A hundred eyes on your codebase."
An MCP server that gives any AI agent complete situational awareness of a codebase — security, quality, architecture, type safety, git history, and dead code — with zero infrastructure.
No server. No database. No CI plugin. No API keys. No data leaves your machine.
npx @cerionautomation/argus
Why this exists
Ask an AI assistant "is my codebase secure?" and it guesses, because it can only see the file you pasted. It cannot see the other 400 files, run your tests, or check your git history.
ARGUS fixes that. Connect it as an MCP server and the agent gets 24 tools that read the whole repository, score it across 10 dimensions, and return structured JSON it can act on.
ARGUS vs SonarQube
| ARGUS | SonarQube | |
|---|---|---|
| Setup | npx @cerionautomation/argus |
Server + PostgreSQL + CI plugin + admin account |
| Infrastructure | None | Dedicated host, DB, JVM |
| Cost | Free, MIT | £15k–£150k/year enterprise |
| Consumer | AI agents (structured JSON) | Humans (HTML dashboard) |
| Scan speed | 68ms security scan on 99k lines | Minutes; full analysis 10–30 min |
| Autonomous fixing | Yes — self-healing loop | No |
| False-positive transparency | critique_report shows every rejection + reason |
Manual triage in the UI |
| Git churn hotspots | Built in | Requires plugin/commercial edition |
| Dead export detection | Built in | Limited |
| RAG code retrieval | Built in (local BM25) | Not available |
| Privacy | 100% local | Server-side, often cloud |
| Offline | Works | Needs the server |
Where SonarQube still wins: 30+ language support (ARGUS focuses on TS/JS/Python/Go), decades of rule tuning, compliance certifications, and multi-team dashboards with historical trend reporting. ARGUS is not trying to replace an enterprise quality-gate deployment — it replaces the feedback loop between an AI agent and your code.
Accuracy: measured, not claimed
Most scanners drown you in false positives. ARGUS validates every finding against its own evidence and rejects the ones that don't hold up.
Real result on a 99,681-line Next.js production codebase:
| Detector generation | Findings | True positives | Precision |
|---|---|---|---|
| Naive regex (v0) | 7 | 3 | 43% |
| Multi-gate + semantic critique (v1) | 3 | 3 | 100% |
The four eliminated false positives were:
"select your dates"in FAQ prose flagged as SQL injectionselect=accessTokenin a REST URL flagged as SQL injection- A
console.logflagged as a hardcoded credential (correctly reclassified as secret-logging)
Every rejection is inspectable via critique_report.
How the accuracy works
1. Multi-gate detection. A SQL injection finding requires three independent gates:
- A well-formed SQL statement (
SELECT … FROM, not the word "select") - A query executor within 2 lines (
.query(,$queryRaw,knex.) - Not a URL or REST query string
2. Entropy checks on secrets. A credential must have a known key prefix (sk-, ghp_, AKIA, AIza) or genuine entropy — mixed case, digits, 20+ chars. Interpolated values, env references, and type declarations are excluded.
3. Semantic critique. Each surviving finding is re-examined against its own captured evidence. If the evidence contradicts the claim, it is rejected with a stated reason.
4. Honest confidence. The confidence number is the share of findings marked confirmed rather than possible — not a cosmetic 100%.
Tools (24)
Diagnosis
full_diagnose— everything at once: score, findings, hotspots, dead code, typesquantum_score— 10-dimension weighted grade (S/A/B/C/D/F), reproducibleswarm_intel— all scanners in parallel + critique loopcheat_sheet— ~150 token repo orientation for an agent
Security
security_scan— secrets, SQLi, XSS, path traversal, weak crypto, CORS, open redirect, prototype pollution, TLSstandards_check— OWASP Top 10, SOLID, 12-Factor, Clean Architecturedependency_risk— risky packages, wildcard versions, missing lockfile
Quality
code_quality— empty catch, console.log,@ts-ignore,any, oversized filestype_coverage— TypeScript strictness scorememory_scan— listener leaks, missinguseEffectcleanup, timer leakstest_coverage— ratio, assertion-free tests, skipped testsdead_exports— exported symbols nothing imports
Git intelligence
git_hotspots— files with highest 90-day churn (churn correlates with bugs)
RAG grounding
rag_retrieve— BM25 code retrieval, local, zero API callsground_finding— full enclosing function + every caller of a symbolcritique_report— every rejected false positive with its reason
Action
auto_diagnose— self-healing loop: diagnose → fix → re-score → iterateverify_all— build, lint, test with captured outputrisk_assess— 4-dimension risk → Full Autonomy / Mixed / Structured modegap_analysis— missing CI, linter, README, tsconfigsearch— ripgrep-powered, 32× faster than grepthink— structured chain-of-thought scaffoldmemory_set/memory_get— cross-session persistence
3 prompts: deep_audit, production_gate, debug_root_cause
3 resources: argus://{path}/health, /summary, /hotspots
Install
Claude Code
claude mcp add argus -- npx -y @cerionautomation/argus
Claude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"argus": {
"command": "npx",
"args": ["-y", "@cerionautomation/argus"]
}
}
}
From source
git clone https://github.com/CerisonAutomation/argus-mcp
cd argus-mcp && npm install && npm run build
Engineering
- Zero runtime dependencies beyond the MCP SDK and Zod
- Circuit breakers on every scanner — an agent never hangs
- Memory-safe walker — 30MB total / 500KB per file caps, depth-limited
- Sanitised exec —
execFileSyncwith argument arrays, nevershell: true - Strict TypeScript —
exactOptionalPropertyTypes,noUncheckedIndexedAccess - MCP Spec 2025-06-18 — tool annotations, structured content, output schemas
Benchmarks
Measured on a 99,681-line / 631-file Next.js + TypeScript production codebase:
| Tool | Time |
|---|---|
cheat_sheet |
146ms |
security_scan |
68ms |
quantum_score |
189ms |
git_hotspots |
24ms |
rag_retrieve |
111ms |
dead_exports |
286ms |
Licence
MIT © Cerison Brown
Built by Cerison Brown — SDET | QA Automation Engineer | AI Workflow & Systems Automation Engineer
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。