Repo Run Check
Related Servers
Alternatives to Repo Run Check
No user-submitted related servers found.
Related 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- AlicenseAqualityBmaintenanceSecurity checks for code an AI agent is about to trust. vetcode_guard checks a command before it installs packages or adds an MCP server: made-up names, look-alikes, malware advisories, brand-new releases, and the archive read without running it. vetcode_scan reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets and risky config. Local, zero dependencies.42MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to scan projects or changed files for risky leftovers like hallucinated packages, exposed secrets, truncated code, and unfinished stubs, and to verify that packages exist before installing them.17 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to check npm packages, GitHub Action refs, and remote scripts before execution, returning deterministic ALLOW/DENY/REVIEW verdicts with evidence and a re-checkable manifest.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to inspect local and remote repositories through sandboxed tools that surface project overviews, structure, dependency audits, Git churn hotspots, and a heuristic health score. It also supports safe GitHub issue searching and creation with built-in duplicate preflight checks, while blocking sensitive files, binary content, and path traversal attacks.22 npmMIT
- AlicenseAqualityBmaintenanceGives AI agents six pre-action security checks — code audits, dependency existence and safety, prompt-injection detection, reversible-command analysis, domain trust, and passive site scanning — each returning a pass/review/block verdict with supporting evidence so the agent can branch automatically. Runs as a single dependency-free stdio server compatible with Claude Desktop, Cursor, Cline, Windsurf, and Continue.6MIT
TDQS
Scored across 3 tools
Each tool targets a distinct input surface: a single command, a local cloned folder, or a remote GitHub repo. Descriptions explicitly cross-reference each other ('For a whole cloned folder use check_local_repo. For a GitHub repo that is not cloned yet use check_repo'), leaving no ambiguity about which to pick.
All three tools follow the same check_<target> verb_noun pattern (check_command, check_local_repo, check_repo), with clear and predictable scope implied by the noun. No mixed conventions or stray verbs.
Three tools map exactly to the three realistic input types (command line, local folder, remote repo), each earning its place with no redundancy. The set is well-scoped for a focused static scanner rather than padded with variants.
The lifecycle (check before running/cloning) is covered across three input surfaces, and the tools clearly state their limits (local scan reads only a fixed file list; remote scan reads only the README). Minor gaps exist for non-GitHub URLs or installing from package registries, but agents can generally fall back to check_command or check_local_repo.