vet is a software supply-chain security tool that examines open-source packages for malware, vulnerabilities, license issues, and policy violations. Developers use it to scan package manifests, repositories, container images, or SBOMs and to enforce security policies in CI/CD systems.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/safedep/vetWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/safedep/vet/vet-mcp)<a href="https://agentmods.dev/mcp/safedep/vet/vet-mcp"><img src="https://agentmods.dev/badge/mcp/safedep/vet/vet-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/safedep/vet/vet-mcp"><img src="https://agentmods.dev/badge/mcp/safedep/vet/vet-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vet-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"vet-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/safedep/vet:v1.12.13",
"--rm",
"-i"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 14 lines scan A 47526401553b
vet-mcp is an MCP server published in the GitHub repository safedep/vet (1,104 stars, last pushed 7d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
zyrax-guard
Audit AI agent configs for prompt injection & rogue MCP servers; vet packages. Runs locally from the zyrax-guard npm package.
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
local-dev
MCP server "local-dev", hosted remotely at localhost, as configured in akanthed/SecureAI-Scan.
draugr
MCP server "draugr" as configured in draugr-dev/draugr. Launched with https://github.com/draugr-dev/draugr/releases/download/v0.99.1/draugr-0.99.1.mcp.
sswp-mcp
MCP server "sswp-mcp" as configured in VrtxOmega/sswp-mcp. Runs locally from the sswp-mcp npm package.
matrixscroll
MCP server for signed machine-action records, offline tool-surface checks, and SSX360 USB signer support. Runs locally from the matrixscroll Python package.