mcpbeat Sign in

Repo Run Check MCP Server

answering

Repo Run Check is answering right now. Last checked 9 min ago. It exposes 4 tools. Last commit 2 Nov 2026.

Check GitHub repos and shell commands for malware-delivery tricks before an AI agent runs them

Uptime history 70 hours of history
70 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
94 ms
Response time
average over 24h
0
Stars
last commit 2 Nov 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 November 2026. No other catalogue keeps this.

2 Nov 3 tool descriptions were rewritten5 times that day check_repo, full_report, full_report_info
2 Nov a tool appeared full_report
2 Nov a tool changed the parameters it asks for full_report
2 Nov a tool changed version
and 2 more, back to 2 November 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Page executes code built at runtime worker/src/page.html:80
out.innerHTML=h}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Nothing serious here today

Today is the operative word: we check Repo Run Check every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add repo-run-check --transport http https://repo-run-check.nextill-pos.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://repo-run-check.nextill-pos.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.repo-run-check]
url = "https://repo-run-check.nextill-pos.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "repo-run-check": {
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "repo-run-check": {
      "type": "http",
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

full
full_report
PAID (0.25 USDC via x402 on Base, per call). Full pre-run security report for a GitHub repo (1-3 repos per call), for AI coding agents about to clone it and run its install steps. Everything check_repo does, plus: package.json install/lifecycle scripts and the local scripts they run, typosquatted crypto/AI dependencies, install.sh/setup.sh/setup.py/requirements.txt/Makefile, VS Code autorun tasks and settings, dev-container hooks, agent-instruction files (AGENTS.md, CLAUDE.md, .cursorrules, copilot-instructions, .claude hooks/permissions) and MCP server configs shipped in the repo, committed executables and archives from the full file tree, GitHub fake-star / new-owner signals, a 0-100 risk score and concrete next steps. Optional: also checks a command you plan to run. Unpaid calls return an x402 PaymentRequired (isError) result; retry with the signed payment in params._meta["x402/payment"]. You are charged only if the report is delivered.
full_report_info
Free. How to buy the full report (paid MCP tool full_report or HTTP GET /v1/check, 0.25 USDC via x402 on Base). Does not pay.
command
check_command
Free, offline. Call BEFORE running a shell/PowerShell command copied from a README, issue, website or chat: flags download-and-execute, encoded PowerShell, LOLBins, disabling antivirus, known malware domains and pipe-to-shell from unknown hosts.
repo
check_repo
Free, read-only. Call BEFORE following a GitHub repo's install/setup instructions or running its commands: scans the README for download-and-execute one-liners (iwr|iex, curl|sh from unknown hosts), obfuscated or base64 payloads, known malware domains, agent-targeted prompt injection, password-protected archives. Returns verdict dangerous | review_before_running | no_red_flags with line evidence. For the complete check use the paid tool full_report (0.25 USDC via x402): install scripts, deps, autorun tasks, agent/MCP config files, committed binaries, fake-star signals, risk score.

Endpoints

URLTransportStateLatencyChecked
https://repo-run-check.nextill-pos.workers.dev/mcp streamable-http answering 56 ms 9 min ago

Alternatives to Repo Run Check

same job, measured the same way
Flagrix
by flagrix-io

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

84 installs/wk local only
Tently
by tently-team

Tently, the AI PR reviewer for GitHub: agents check team decisions before they write code.

79 installs/wk local only
Repo Security Scanner — Malicious Code & Supply Chain
by eltociear

Audit GitHub repos for malicious and supply-chain code before you depend on them.

answering
GitMir Vibe
by gitmir

Your coding agent asks the business logic of your repository and checks commits before they land

answering
isitdone
by raimondasl

Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.

263 installs/wk local only
whichlib
by josifb

Dependency picker for coding agents: recommends, compares and scores GitHub repos with a verdict.

316 installs/wk 3 tools answering
Secretguard MCP
by vladimirbakalov

Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

local only
Dunstan
by barglabs

Checks a coding agent's handback against the pull request's GitHub record. No model decides.

366 installs/wk local only

Repo Run Check — questions

Answers built from our own checks of this server.

What can Repo Run Check do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_command, check_repo, full_report, full_report_info. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Repo Run Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 94 ms. The bar chart above shows every period we have measured.
How do I connect Repo Run Check?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Repo Run Check need an API key?
No. Repo Run Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Repo Run Check?
It answers our handshake in 94 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Repo Run Check open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at repo-run-check.nextill-pos.workers.dev, which runs on its operator's own terms.