Argus - Repository Analysis and Security Assessment Tool

Created By
athaponga year ago
A Model Context Protocol (MCP) server for analyzing GitLab repositories and performing security assessments.
Overview

What is Argus?

Argus is a Model Context Protocol (MCP) server designed for analyzing GitLab repositories and performing security assessments, focusing on code quality across multiple programming languages.

How to use Argus?

To use Argus, install it via the command line and run various MCP commands to analyze repository structures, perform code quality checks, and conduct security scans on your GitLab repositories.

Key features of Argus?

  • Multi-language support for Go, Java, Python, and JavaScript/TypeScript.
  • Integrated security scanning with Trivy for vulnerability assessments.
  • Git operations including branch management and commit history analysis.

Use cases of Argus?

  1. Analyzing code quality in multi-language projects.
  2. Performing security scans to identify vulnerabilities in code repositories.
  3. Visualizing repository structures and managing branches effectively.

FAQ from Argus?

  • What languages does Argus support?

Argus supports multiple languages including Go, Java, Python, and JavaScript/TypeScript.

  • Is Argus free to use?

Yes! Argus is open-source and free to use under the MIT License.

  • How do I install Argus?

You can install Argus using the command uvx argus after ensuring you have the necessary system dependencies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
athapong
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago