Vet vs Lazaretto MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vet vs Lazaretto MCP
In-depth architectural comparison of the Vet and Lazaretto MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Vet
Security · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Lazaretto MCP
Security · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Vet if you need specialized Security tools running via a local process. Choose Lazaretto MCP if your workspace requires Security integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Vet when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
vet-mcp checks open source packages—like those suggested by AI coding tools—for vulnerabilities and malicious code. It supports npm and PyPI, and runs locally via Docker or as a standalone binary for fast, automated vetting.
Check whether anything you depend on is known malware, before an agent installs it. checklockfile takes a package-lock.json, yarn.lock or pnpm-lock.yaml and matches every pinned version against published malicious-package advisories in one call, free and with no API key, catching compromised releases like chalk@5.6.1 while leaving their clean releases alone. scanartifact adds deterministic behavioral analysis (no LLM in the serving path) for credential theft, exfiltration, obfuscation, prompt injection and install-time droppers, with the file, line and evidence that triggered it; verdicts are SHA-256-bound so you can re-verify what landed on disk. Paid scans settle at $0.03 USDC on Base (x402) or prepaid credits. npx lazaretto-mcp
Tools & Capabilities Breakdown
Vet Tools (5)
npm package vetting
PyPI package vetting
Vulnerability checks
Malicious package detection
Local Docker or standalone execution
Lazaretto MCP Tools (2)
known_bad_lookup
scan_artifact
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Vet is categorized under Security and uses a local stdio subprocess. In contrast, Lazaretto MCP belongs to Security using remote streaming HTTP/SSE transport. Select Vet when you need capabilities focused on security and Lazaretto MCP when you require tools for security.