Log inSubmit server
Flagrix logo

Flagrix

Scans GitHub repositories and profiles for malware, dependency risks, and scam signals before agents clone code.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Flagrix

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "flagrix": {
      "command": "npx",
      "args": [
        "-y",
        "flagrix"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y flagrix

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 9d ago.

Overview

The flagrix MCP server exposes GitHub repository and user-profile scanning to AI agents through stdio. Its checks produce risk assessments tied to the exact commit scanned, helping agents review code before cloning it. Reach for flagrix when an agent may encounter untrusted repositories, coding assignments, or suspicious developer profiles. Scans run locally, while GitHub, npm, and detection-rule requests provide the external data required for analysis.

Use cases

  • Scan repositories before an agent clones unfamiliar code
  • Score GitHub profiles involved in coding-assignment workflows
  • Gate git clone operations with a Claude Code hook
  • Check dependencies against a local malicious-package feed

Key features

  • Commit-pinned GitHub repository verdicts
  • GitHub profile scam-signal scoring
  • MCP tools for repository and user scans
  • Local OSV malicious-package matching
  • Private-repository scanning with a GitHub token
  • JSON output and risk-based exit codes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

11/11 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · flagrix (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads271Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Flagrix works

What flagrix MCP server does

flagrix scans GitHub repositories before they are cloned and evaluates GitHub profiles for scam-related signals. Its MCP interface provides two agent tools: scan_github_repo and scan_github_user. Repository results include a risk verdict, security score, scanned-file and dependency counts, detected issues, and the commit SHA used for the assessment.

The repository scanner is intended for situations where source code may be hostile, including fake recruiting assignments and unfamiliar public projects. It can identify patterns associated with data exfiltration and other malicious behavior, and it checks dependencies against a curated malicious-package feed.

Verdicts are risk assessments rather than definitive fraud determinations. They should be verified through official channels before a high-impact decision.

How it works

The scanner reads repository files at a specific commit. A branch or other ref resolves to a commit, and the resulting verdict records that commit SHA. This prevents a repository push during or after a scan from silently changing the code represented by the result.

Scanning logic comes from @flagrix/scanner-core, with signatures maintained in the flagrix-detection-rules repository. Detection rules are refreshed and cached for six hours, and a bundled snapshot allows scanning to continue offline with the included rules.

Dependency names are matched locally against osv-malicious.json, a feed of npm and PyPI packages confirmed malicious by the OpenSSF malicious-packages project. The feed is also cached for six hours and revalidated with its ETag. Network requests go to GitHub and npm APIs, plus the public detection-rules repository; the tool does not send dependency names to a Flagrix backend.

Setup and configuration

Run the MCP process through npx:

Terminal
claude mcp add flagrix -- npx -y flagrix mcp

The MCP command uses stdio, so it can be registered with an MCP-compatible client that launches local processes. The command-line package also offers direct scanning with flagrix scan <url | owner/repo> and profile scoring with flagrix scan-user <username>.

Unauthenticated GitHub access is limited to 60 requests per hour. A repository scan may use one request per file, up to approximately 50 requests. Set GITHUB_TOKEN or FLAGRIX_GITHUB_TOKEN to raise the GitHub limit to 5,000 requests per hour and enable private-repository scans. A token can also be supplied with the CLI's --token option.

Set FLAGRIX_OSV_FEED=0 to disable the OSV malicious-package feed. The curated signatures remain active when this feed is disabled.

Tools and capabilities

  • scan_github_repo: scan a GitHub repository for malicious code, dependency risks, and related issues.
  • scan_github_user: score a GitHub profile for scam signals.
  • Commit-pinned repository results with the scanned commitSha.
  • Local matching against the cached OSV malicious-package feed.
  • Access to private repositories when a suitable GitHub token is configured.
  • A Claude Code hook is included for gating git clone operations on a scan.

The CLI supports --json; JSON output is selected automatically when standard output is piped. Exit codes distinguish low risk, scan failure, medium risk requiring review, and high risk where cloning should be avoided.

Limitations and notes

Unauthenticated scans consume GitHub's shared request budget, so large repositories or repeated scans can encounter rate limits. Detection results depend on the available signatures and malicious-package data, including the six-hour refresh and the bundled offline snapshot.

A risk verdict is not proof of fraud or safety. Review findings and confirm the repository or profile through trusted, official channels before proceeding. The project is licensed under MIT, as are the scanner-core and detection-rules components referenced by the project.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Flagrix

flagrix is an MCP server that connects AI agents to GitHub scanning workflows through stdio. Its main tools, `scan_github_repo` and `scan_github_user`, assess repositories for malware and dependency risks and score profiles for scam signals, with repository verdicts pinned to the scanned commit.

Install it through `npx` with `claude mcp add flagrix -- npx -y flagrix mcp`. This registers the stdio MCP process with Claude, while the package also supports direct `flagrix scan` and `flagrix scan-user` commands.

Yes, flagrix can scan private repositories when you provide a GitHub token. Set `GITHUB_TOKEN` or `FLAGRIX_GITHUB_TOKEN`, or pass a token with the CLI's `--token` option; authentication also raises the GitHub request limit.

flagrix reads files at a resolved commit and includes that commit's SHA in the result. A later push therefore cannot silently change which repository contents the verdict represents.

Yes, flagrix uses a standard stdio MCP process and can be launched by MCP-compatible clients such as Cursor. Configure the client to run `npx -y flagrix mcp`.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFlagrix AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/flagrix?style=directory)](https://allmcps.com/mcp/flagrix)
HTML Embed
<a href="https://allmcps.com/mcp/flagrix"><img src="https://allmcps.com/api/badge/flagrix?style=directory" alt="Flagrix on AllMCPs" /></a>