In-depth architectural comparison of the Lazaretto MCP and Agentscore MCP Server 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
Lazaretto MCP
Security · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: API Key required
Agentscore MCP Server
Security · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lazaretto MCP if you need specialized Security tools running via a hosted cloud SSE transport. Choose Agentscore MCP Server if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lazaretto MCP when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: LAZARETTO_API_KEY, LAZARETTO_BASE_URL.
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
Lazaretto MCP Tools (2)
known_bad_lookup
scan_artifact
Agentscore MCP Server Tools (8)
scan_package
Scan an npm package for MCP security issues. Checks install scripts, prompt injection patterns, suspicious URLs, source code patterns, dependency count, metadata completeness, and publisher provenance. Returns score (0-100), risk level, and detailed findings.
get_verdict
Get a trust verdict for an MCP package: allow, warn, or block. Based on scan findings (score and severity). Also reports monitoring status and publisher posture. Use this before installing or connecting to an MCP server.
check_exposure
Check which monitored MCP servers depend on a given package. Use this during incident response to find blast radius. Example: 'which MCP servers use axios?'
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).
Lazaretto MCP is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Agentscore MCP Server belongs to Security using local stdio subprocess. Select Lazaretto MCP when you need capabilities focused on security and Agentscore MCP Server when you require tools for security.
Check if a package or agent has been reported to the KYA abuse database. Returns whether abuse has been reported and any details.
monitor_status
Check if an MCP package is under continuous monitoring and get its scan history. Shows current score, risk level, and recent changes.
check_my_repo
Inspect the current repo for MCP dependencies, look up AgentScore verdicts for each package, and summarise what should be gated in CI. Use this when a developer wants to understand all MCP packages in a repo instead of scanning one package at a time.
generate_policy_gate_setup
Generate the exact GitHub Actions workflow needed to enforce AgentScore Policy Gate for a repo. Detects MCP dependencies locally and returns the OIDC-based YAML needed for setup. No API key or secret is required.
install_policy_gate
Write the AgentScore Policy Gate workflow file to this repo. Creates .github/workflows/agentscore-policy-gate.yml with OIDC authentication (no API key needed). Detects MCP dependencies and includes them in the workflow. The gate will auto-provision the repo on first push.