Repo Run Check

Statically scans one shell, bash or PowerShell command (or a short script) for malware-installer patterns before anyone runs it. Use it whenever an agent is about to run a command copied from a README, issue, gist, website, chat or AI answer, and for one-liners like curl | sh or iwr | iex. It flags download-and-execute (curl/wget piped to a shell, iwr/irm piped to iex) from unknown hosts, encoded or obfuscated PowerShell, Windows LOLBins (mshta, certutil, rundll32...), commands that disable antivirus or Defender, and known malware domains. Well-known installers (rustup, Foundry, Anza and similar) are reported as info only. Offline: nothing is sent anywhere and the command is never executed. Returns verdict: no_red_flags (nothing matched; not proof of safety), review_before_running (at least one warning: read the flagged lines first) or dangerous (download-and-execute, encoded payloads, known malware hosts and similar: do not run), plus findings (level, code, message, line, evidence). For a whole cloned folder use check_local_repo. For a GitHub repo that is not cloned yet use check_repo.

Statically scans a repository folder on the machine running this MCP server before you run npm install, pip install, make or its setup steps. It reads only these files if present (each up to 300 KB): README.md, package.json, install.sh, setup.sh, setup.py, requirements.txt, .vscode/tasks.json and Makefile. It looks for npm lifecycle scripts (preinstall/postinstall) that download or run code, typosquatted or URL dependencies, setup.py side effects, VS Code tasks that autorun on folder open, and dangerous commands in the README and scripts. Read-only: it never executes anything, never writes files and sends nothing over the network. Other source files are not inspected, so this is not a full malware scan. Returns verdict: no_red_flags (nothing matched; not proof of safety), review_before_running (at least one warning: read the flagged lines first) or dangerous (download-and-execute, encoded payloads, known malware hosts and similar: do not run), plus advice, files_checked, findings (level, code, message, file, line, evidence) and install_commands found in README code blocks. Use check_repo instead when the repo is only on GitHub and not cloned yet.

Fetches a public GitHub repo's README (raw.githubusercontent.com, up to 300 KB) and scans its install instructions before you clone it or follow them. Use it when a user or agent is told to 'clone this repo and run the setup' or is evaluating a starter kit, trading bot, wallet tool or MCP server from GitHub. Free and read-only: one unauthenticated HTTPS request to GitHub; nothing is cloned or executed. Only the README is checked here. The optional paid hosted check (https://repo-run-check.nextill-pos.workers.dev/v1/check, 0.005 USDC via x402 on Base) also reads package.json install scripts, dependencies, setup files and repo metadata such as age and fake-star signals. This tool does not pay for it; it only returns its URL. Returns verdict: no_red_flags (nothing matched; not proof of safety), review_before_running (at least one warning: read the flagged lines first) or dangerous (download-and-execute, encoded payloads, known malware hosts and similar: do not run), plus repo, url, advice, files_checked, findings, install_commands, tier, full_report (URL of the paid check) and full_report_price_usdc. Errors if the repo is private, renamed or missing. If the repo is already cloned, check_local_repo covers more files at no cost.