Shieldapi MCP vs Lazaretto MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shieldapi MCP vs Lazaretto MCP
In-depth architectural comparison of the Shieldapi MCP 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
Shieldapi MCP
Security · Local stdio
Quality: 56/100 (Good) | Auth: other
Lazaretto MCP
Security · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Shieldapi MCP 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 Shieldapi MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Freemium).
You have access to required keys: SHIELDAPI_URL, SHIELDAPI_WALLET_PRIVATE_KEY.
Security intelligence for AI agents: password breach checks (900M+ HIBP hashes), email/domain/IP/URL reputation, prompt injection detection (200+ patterns), and skill supply chain scanning. Pay-per-request via x402 USDC micropayments or free demo mode, no API key needed.
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
Shieldapi MCP Tools (10)
check_url
Check a URL for malware, phishing, and other threats. Uses URLhaus + heuristic analysis.
check_password
Check if a password hash (SHA-1) has been exposed in known data breaches via HIBP.
check_password_range
Look up a SHA-1 hash prefix in the HIBP k-Anonymity database.
Shieldapi MCP is categorized under Security and uses a local stdio subprocess. In contrast, Lazaretto MCP belongs to Security using remote streaming HTTP/SSE transport. Select Shieldapi MCP when you need capabilities focused on security and Lazaretto MCP when you require tools for security.
Run all security checks on a target (URL, domain, IP, or email). Most comprehensive scan.
scan_skill
Scan an AI agent skill/plugin for security issues across 8 risk categories (Snyk ToxicSkills taxonomy). Checks for prompt injection, malicious code, suspicious downloads, credential handling, secret detection, third-party content, unverifiable dependencies, and financial access patterns. Static analysis only — no code execution. Returns risk score (0-100), severity-ranked findings with file locations, and human-readable summary.
check_prompt
Detect prompt injection in text. Analyzes across 4 categories (direct injection, encoding tricks, exfiltration, indirect injection) with 200+ detection patterns. Designed for real-time inline usage before processing untrusted user input. Returns boolean verdict, confidence score (0-1), matched patterns with evidence, and decoded content if encoding obfuscation was detected. Response time <100ms p95.
check_mcp_trust
Get a multi-signal trust score for any MCP server endpoint. Analyzes security (domain reputation, SSL, SPF/DMARC), injection risk (tool description scanning), supply chain safety (toxic skill categories), reliability (uptime, latency, protocol compliance), and on-chain reputation (AgentProof ERC-8004). Returns composite trust score (0-100), tier (platinum/gold/silver/bronze/unranked), and detailed per-signal breakdown. Use this to evaluate whether an MCP server is safe to connect to.