Repo Run Check
Server Details
Check GitHub repos and shell commands for malware-delivery tricks before an AI agent runs them
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- devx-agent/repo-run-check
- GitHub Stars
- 0
- Server Listing
- Repo Run Check
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
check_command and check_repo clearly target different inputs (a shell command vs. a GitHub repo), and full_report_info is obviously the payment/docs helper. The only fuzzy boundary is check_repo vs. full_report, which overlap by design as free vs. paid tiers, but the description makes the upgrade path explicit.
Names fall into two readable clusters: the check_* verb_noun scanners and the full_report/full_report_info pair. Both are snake_case and self-explanatory, though the mixing of a verb-prefixed family with a noun-based paid family is a minor deviation.
Four tools map cleanly onto the narrow workflow: scan a command, scan a repo, buy the deep report, learn how to pay. Slightly thin overall, and full_report_info is essentially documentation rather than a capability, but nothing is redundant or missing at this scope.
The surface covers the core pre-run safety workflow end to end, including the paid upgrade and its purchase mechanics via x402. Minor gap: no tool for checking non-GitHub sources (e.g. arbitrary URLs or archives) beyond the command-level scan.
Available Tools
4 toolscheck_commandARead-onlyInspect
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.
Inputs: cmd (required).
check_repoARead-onlyInspect
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.
Inputs: repo (required).
full_reportARead-onlyInspect
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.
Inputs: repo, repos, command.
full_report_infoARead-onlyInspect
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.
Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools.
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
Package verdicts for AI coding agents: check npm, PyPI, Go and NuGet installs before they run.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to scan GitHub repositories and user profiles for malware signals before cloning, providing risk verdicts pinned to specific commits.181 npm2MIT- AlicenseNot gradedqualityCmaintenanceA runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.1MIT
- AlicenseNot gradedqualityCmaintenanceReal security scanners for AI coding agents — SAST (441 rules), secret detection (419+ patterns), dependency CVEs (OSV.dev), MCP/skill vetting, MITRE ATT&CK. Open-source, Rust, free11 npmApache 2.0
- AlicenseAqualityDmaintenanceVerify-before-act safety tools for AI coding agents, providing MCP tools to check packages, lockfiles, manifests, and CI workflows for supply chain risks.4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.