Fake Star Audit MCP server
io.github.Armada735/fake-star-audit·v0.1.1Transparent rule-based GitHub fake-star detector — LOW/MEDIUM/HIGH with per-rule evidence.
0 stars47 downloads/wk
Reviews
Write oneNobody has reviewed Fake Star Audit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Fake Star Audit tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
audit_repoAudit a GitHub repository's stargazers for signs of fake-star injection.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 122 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
How Fake Star Audit compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 50% of 1,119 Developer tools servers
- Tools
- 1
- the typical Developer tools server has 7
- Tools that change things
- 0%
- typical: 5%. Fewer write tools means less an agent can break
- Downloads a week
- 47
- more than 35% of 436 Developer tools servers with a package
What its tools let an agent do: 1 read
Install Fake Star Audit in Claude Code, Cursor or VS Code
claude mcp add fake-star-audit -- uvx fake-star-audit
What the publisher says
From the Fake Star Audit repository's README, as published. We do not edit it. Read it on GitHub
fake-star-audit
<!-- mcp-name: io.github.ardev-lab/fake-star-audit -->
A transparent, dependency-free GitHub fake-star checker. One Python file, no token, no install — point it at a repo and get a LOW / MEDIUM / HIGH risk verdict with every rule explained.
$ python3 audit.py --repo someowner/somerepo
🔴 someowner/somerepo — risk: HIGH
422★ / 0 forks / age 66.9h
windows: earliest=100, latest=22
axes: page1_sliding_window, sequential_id_cluster, same_second_cluster
[FLAG] page1_sliding_window earliest: BURST: 100 stars in 0.55h (~183 stars/h)
[FLAG] sequential_id_cluster earliest: 4+ time-consecutive stargazers within id range <200k
[FLAG] same_second_cluster earliest: max 4 stars within a 30s windowWhy
GitHub stars are used as a proxy for trust — by investors doing due-diligence, by engineers picking dependencies, by recruiters reading résumés. But there is a paid market for fake stars: bot accounts and "star farms" inflate a repo to look popular. (See the CMU study estimating millions of suspected fake stars.)
fake-star-audit gives you a fast, explainable gut-check: is this repo's star count believable?
What makes it different
There are already excellent fake-star tools — see How it compares. This one is deliberately the smallest, most portable option:
GITHUB_TOKEN or any environment variable, and never writes files.
- Zero dependencies. Pure Python standard library. No pip install.
- No token, no account. Uses the anonymous GitHub API. It never reads your
in natural language and get a structured report.
- One file. Copy audit.py anywhere and run it.
- AI-native. Ships as a Claude Code skill — ask "is this repo fake-starred?"
with its evidence printed.
- Transparent. No machine-learning black box. Every flag is a named rule
It is not trying to replace at-scale academic crawlers or full due-diligence suites. It's the dependency-free, AI-friendly first look.
Quick start
CLI
# no install needed — just the one file
python3 audit.py --repo facebook/react
python3 audit.py --repo facebook/react --json # machine-readableOr install from PyPI (pip install fake-star-audit) and run the fake-star-audit-cli command. Note: the bare fake-star-audit command is the MCP server (see below), not the CLI.
Claude Code skill
Drop the skill/ folder into ~/.claude/skills/ (see skill/SKILL.md), then in Claude Code:
You: is github.com/someowner/somerepo fake-starred?
Claude: HIGH risk — 100 stars landed in the first 33 minutes after the
repo was created, with near-sequential account IDs. That's a bootstrap
injection pattern, not organic growth.
MCP server (Claude Desktop, Cursor, …) — optional
An optional MCP wrapper exposes the audit as the auditrepo tool. It runs over stdio** — your MCP client launches it as a local subprocess; it opens no network server and reads no environment variables.
Easiest — via the package (uvx). Published on PyPI as fake-star-audit and in the MCP Registry as io.github.ardev-lab/fake-star-audit. Register it with your client, e.g. Claude Desktop's claudedesktopconfig.json:
{
"mcpServers": {
"fake-star-audit": {
"command": "uvx",
"args": ["fake-star-audit"]
}
}
}From a local checkout. Requires Python 3.10+ and the mcp package (the core audit.py itself needs neither):
pip install -r requirements.txt # installs `mcp`{
"mcpServers": {
"fake-star-audit": {
"command": "python3",
"args": ["/absolute/path/to/fake-star-audit/mcp_server.py"]
}
}
}Now ask your assistant "audit the stars on owner/repo" and it will call the audit_repo tool.
How it works
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Fake Star Audit: common questions
- Is Fake Star Audit MCP server safe?
- Mostly: it is graded B (78/100). Read the Fake Star Audit safety report
- How do I install Fake Star Audit?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Fake Star Audit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Fake Star Audit maintained?
- The last commit was 160 days ago (2026-05-28). The latest release is v0.1.1.
- What can I use instead of Fake Star Audit?
- Servers from other publishers that do the same job: Mason MCP server, GitDiagram MCP server and GitHub MCP server.
- How does Fake Star Audit compare with other Developer tools MCP servers?
- safety score 78/100 (higher than 50% of 1,119 Developer tools servers); tools 1 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Fake Star Audit
Same job from other publishers: the closest match first, then the best rated.
- MasonEngineering decisions, change impact, documentation audits, and CI evidence for coding assistants.not reviewedGrowingA
- GitDiagramArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.not reviewedEstablishedA
- GitHubConnect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.not reviewedEstablishedA
Gk CLIThe GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.not reviewedEstablishedB- Agent HarnessesAgent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.not reviewedEstablishedA