GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Security check for coding agents: malware, supply chain, secrets and web bugs. Reads, never runs.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use vetcode and tell me what you can do for me, then show me one thing✓ If Claude says it is using vetcode or shows a vetcode tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect vetcode yet
vetcode runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect vetcode
B · Others in Cybersecurity that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect vetcode yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect vetcode
Cursor cannot connect vetcode yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect vetcode
VS Code cannot connect vetcode yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect vetcode
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026
The registry name was verified with the GitHub account openyard-cloud, which owns the repo
Code last changed 3 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/openyard-cloud-vetcode)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 days ago, and the latest version (0.8.7) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: GitHits, Dependency Management MCP Server, Snyk MCP, Draugr, Spotdb
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sonatype component intelligence: versions, security analysis, and Trust Score recommendations
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
Ephemeral data sandbox for AI workflows with guardrails and security
| This one vetcode | GitHits | Dependency Management MCP Server | Snyk MCP | Draugr | Spotdb | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Installs on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 5/5 | 3/4 | 3/3 | 3/3 | 3/3 |
| License | MIT | Apache-2.0 | – | Apache-2.0 | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
vetcode
The security check your AI coding agent runs before it acts. Before it installs a package, after it clones a repository, before your code ships. Zero dependencies. Reads, never runs. Works without an agent too.
# Claude Code: the skill plus the guard that checks installs and clones
claude plugin marketplace add openyard-cloud/vetcode && claude plugin install vetcode@openyard
npx skills add openyard-cloud/vetcode # any other agent, as a skill npx github:openyard-cloud/vetcode#v0.8.7 . # no agent: scan a project, a package or a cloned repo
An agent installs a package in a second and runs a cloned project without reading it. vetcode is the check in between. It is three things:
| What it does | Where it runs | |
|---|---|---|
| The guard | Answers allow, ask or deny before a package is installed or an MCP server is added, and reads a repository right after it is cloned | Claude Code, on its own; other agents call it as a tool |
| The scanner | Reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets, and server and CI problems, and lists the places in web code worth reading | Skill, MCP server, command line, GitHub Action |
| The review procedure | Tells your agent how to confirm each finding by reading the code, and what to report | Skill, MCP server |
Nothing from the code it looks at is installed, built or run. It needs Node.js 18 or newer and nothing else. Free and open source (MIT), from the OpenYard community.
Contents: How good is it · Install · The guard · Use it · What it checks · How it works, and its limits
Every number here is measured, on samples the rules were not tuned on unless it says so. The scripts, the runs and the full history are in bench/.
| Question | vetcode | For comparison |
|---|---|---|
| Malicious npm packages caught, of 1,000 (false alarms on 1,000 clean ones) | 947 (26); verdicts 907 (5) | GuardDog: 903 (43) |
| Malicious PyPI packages caught, of 300 (false alarms on 210 clean ones) | 262 (16); verdicts 234 (1) | GuardDog: 241 (48) |
| The same malware after 8 kinds of disguise | still catches 99–100% of what it caught | GuardDog: 90–92% on several |
| Malicious agent skills it had never seen, of 157 (false alarms on 1,029 clean ones) | 91 (1) | Cisco skill-scanner: 101 (56) |
| The guard, shown malware as if nobody had reported it yet | blocks or questions 95% of npm, 88% of PyPI, and 3% of clean npm packages | |
| A package whose newest release is hours old, asked for 3 times | the agent installs the previous, settled version 3 times | the agent alone installs the new release 3 times |
| Wrong "this is malicious" verdicts on 72 real applications (228,000 files) | 1 | |
| Findings an agent has to read on those applications | about 4 per 1,000 files, plus 8 places to read | |
| Real injection bugs the scanner points at, of 480 advisories | 55 (11%); 6% on the half no rule was tuned on | |
| Real authorization bugs found by Claude Code with vetcode, of 49 advisories | 41% | Claude Code alone does as well |
A sign and a verdict are different things. A scanner of several hundred rules that lets any one of them call code malicious is wrong somewhere on almost every large project. vetcode reports every sign, which is what your agent is told to read, and gives a verdict, which is what stops an install without asking, only when a rule with a measured record fires, when two rules agree on one file, or when the sign sits in code an install script starts.
What it is good at. Malware and supply-chain attacks in packages and repositories, attacks aimed at coding agents (poisoned CLAUDE.md and skills, hooks and auto-approved MCP servers in project settings, tool descriptions that give orders), leaked secrets, and stepping in before the install, not after.
What it is not. It does not find web bugs by itself: it lists the dangerous calls as places to read, and those stand at about one real injection bug in ten, so they are where to start, not coverage. It does not make your agent better at logic bugs such as missing authorization; that is the agent's own ability. And a clean report means "nothing obvious found", not "safe".
Read the numbers with care. Samples are 157 to 1,000 items, so they move by a point or two between samples. Most malicious packages in the public datasets were found by GuardDog itself, which favours it. Cisco's scanner catches ten more skills by flagging 56 clean ones, a trade vetcode does not make. All numbers are the scanner alone; in normal use your agent reads every finding again.
All forms need Node.js 18+. vetcode is not on npm: every command here runs it from this repository, pinned to a release. A package called vetcode on npm or PyPI is not this project.
| Your agent | Use |
|---|---|
| Claude Code | the plugin (skill and guard), or the skill alone |
| Gemini CLI | the extension (skill, guard and MCP server) |
| Codex, GitHub Copilot, Cursor, Amp, Goose, opencode, Windsurf, Cline, Roo… | the skill |
| Anything that speaks MCP (Cursor, VS Code, Codex, Gemini CLI, Windsurf, Zed, Claude Desktop, ChatGPT…) | the MCP server |
| claude.ai | the skill zip |
| CI, scripts, or no agent at all | the command line or the GitHub Action |
claude plugin marketplace add openyard-cloud/vetcode && claude plugin install vetcode@openyard
Inside a session the same is two commands, because Claude Code only installs from marketplaces it already knows:
/plugin marketplace add openyard-cloud/vetcode
/plugin install vetcode@openyard
For a whole team
Commit this to the project's .claude/settings.json. Everyone who opens the project and trusts the folder gets the marketplace registered, so each person only runs /plugin install vetcode@openyard once:
{
"extraKnownMarketplaces": { "openyard": { "source": { "source": "github", "repo": "openyard-cloud/vetcode" } } }, "enabledPlugins": { "vetcode@openyard": true } }
The skill, the guard and the MCP server in one install:
gemini extensions install https://github.com/openyard-cloud/vetcode
Gemini CLI downloads the extension from the latest release. Its guard runs before every shell command and file write, like the Claude Code one, with one difference: Gemini CLI has no "ask" answer for a hook, so where Claude Code would ask, you see vetcode's warning and then Gemini CLI's own confirmation of the command. With auto-approval on (--yolo), set VETCODE_GUARD=strict to turn those warnings into a refusal.
For any agent that loads Agent Skills. The skills CLI knows where each agent keeps them (vetcode on skills.sh):
npx skills add openyard-cloud/vetcode
Or copy the folder yourself
git clone https://github.com/openyard-cloud/vetcode, then copy vetcode/skills/vetcode into your agent's skills folder, in the project or under your home folder: .agents/skills/ (shared by many agents, such as Codex and Copilot), .claude/skills/ (Claude Code), .github/skills/ (Copilot), .gemini/skills/ (Gemini CLI) or .cursor/skills/ (Cursor).
Four tools (vetcode_scan, vetcode_guard, vetcode_guide, vetcode_reference) and a security_review prompt. Most agents (.cursor/mcp.json, .mcp.json, Gemini CLI settings.json, Windsurf mcp_config.json):
{
"mcpServers": { "vetcode": { "command": "npx", "args": ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"] } } }
Claude Desktop: download vetcode.mcpb from Releases and open it. The server is also in the MCP Registry as io.github.openyard-cloud/vetcode.
VS Code and Codex
VS Code (.vscode/mcp.json):
{ "servers": { "vetcode": { "type": "stdio", "command": "npx", "args": ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"] } } }
Codex (~/.codex/config.toml):
[mcp_servers.vetcode]
command = "npx" args = ["-y", "-p", "github:openyard-cloud/vetcode#v0.8.7", "vetcode-mcp"]
Then ask your agent to "use vetcode to review this project". The agent should call vetcode_guide once; the server also tells it to.
Download vetcode-skill.zip from Releases and upload it under Settings → Capabilities → Skills.
For tools that read AGENTS.md (or .cursorrules, CONVENTIONS.md…) but neither skills nor MCP, clone this repository next to your project and add:
## Security reviews
When asked to check code for security problems or malware, follow ../vetcode/skills/vetcode/SKILL.md and run its scanner: node ../vetcode/skills/vetcode/scripts/vet.mjs .
An agent decides to install a package in a second: a name it remembered wrong, a name a web page suggested, a release published an hour ago. Installing runs that package's code with your rights. With the Claude Code plugin or the Gemini CLI extension, vetcode looks at every install command before it runs, and at every MCP server before it is registered, and answers allow, ask or deny:
| The command would… | Answer |
|---|---|
| install a package that does not exist (a made-up name is one an attacker can register) | deny |
| install a package with a malware advisory on OSV.dev | deny |
| install a package whose code gets a malware verdict at critical (the archive is downloaded and read, never run) | deny |
| install a package whose code shows signs of malware short of that | ask |
install a name one letter from a popular package (expres, reqeusts) that few people install | ask |
| install a release less than 72 hours old, or one that lost its provenance or gained an install script | ask |
| pipe a download into a shell, or install from another index, a repository or a URL | ask |
| add an MCP server at a tunnel address (ngrok, trycloudflare…) or over plain HTTP to another machine | ask |
| install well-known packages at settled versions | allow, silently |
"Ask" shows you the reason and waits fo