The Lazaretto MCP server and npm package: a free lockfile malware check, plus full scans of npm packages, agent skills and MCP servers.
MCPpedia last refreshed this data
Lazaretto MCP is an MCP server that the Lazaretto MCP server and npm package: a free lockfile malware check, plus full scans of npm packages, agent skills and MCP servers. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 73/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"lazaretto": {
"url": "https://lazaretto.dev/mcp?ref=npm",
"type": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Know what a package or MCP server does before you install or connect it.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in security
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP server for 1Password service accounts — tools and resources for vaults and credentials
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
MCP Security Weekly
Get CVE alerts and security updates for Lazaretto MCP and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Know what a package or MCP server does before you install or connect it.
Lazaretto checks an npm package, an AI agent skill, or an MCP server for malicious behavior. This is the MCP server for it, so your agent can run the check itself.
In Claude, the fastest way is the Lazaretto connector in the Claude directory. Open it and add it. The connector needs no sign-in. It also works in ChatGPT, on some plans.
In Claude Code, one command:
claude mcp add --transport http lazaretto "https://lazaretto.dev/mcp?ref=npm"
For any other client, lazaretto.dev/add has the exact
steps, and Set it up below covers Claude Code, Cursor, Gemini CLI and
Cline. If your client only runs local servers, use npx -y lazaretto-mcp as the
command, which needs Node 20 or newer.
ref=npm only tells us this page is where you found it. Leave it off and nothing
changes.
In a project with a lockfile, ask your agent:
Use the lazaretto
check_lockfiletool to check this project's dependencies.
Or run it in the browser at the free lockfile check, with no account.
The free lockfile check takes each exactly pinned package name and version. It matches them against the OSV and OpenSSF malicious-package advisories, which we sync daily. It does not read the code inside your packages. So it finds a release that has been reported, and it misses a bad release that no one has reported yet. A clean result means nothing matched. It does not prove a package is harmless.
A full scan goes further. A worker with no credentials fetches the package's files, never runs them, and reports what it finds with the file and line. A free key gets 10 scans a day.
This package is a thin front end for the Lazaretto API. It ships no detection logic and only makes HTTPS requests, so you can read it end to end.
Setting this up as an agent, with no other context? Read llms-install.md instead. It is the same information as a straight-line procedure.
| Hosted (recommended) | stdio package | |
|---|---|---|
| Endpoint | https://lazaretto.dev/mcp?ref=npm | npx -y lazaretto-mcp |
| Install | nothing | Node 20 or newer |
| Key goes in | the X-API-Key header | the LAZARETTO_API_KEY env var |
| Get a free key in-session | yes, the get_free_key tool | no, curl the trial endpoint |
| Find a server for a job | yes, the find_mcp_servers tool | no |
| Reads your lockfile off disk | no, you pass the text | yes, from the working directory |
| Needs a client that speaks Streamable HTTP | yes | no |
Eight tools are on both. Their arguments match except for these:
| Tool | stdio package | Hosted |
|---|---|---|
check_lockfile, scan_lockfile_deep | also take path, a lockfile on disk | no path |
scan_artifact | target_type | type, plus name for inline content |
The stdio package refuses an argument a tool does not take, and says what it does take.
The hosted server adds two free tools:
find_mcp_servers, which finds a server for a job in the official MCP registry,
and get_free_key, which mints a free developer key in the session. Pick the hosted one
unless your client has no remote-server support, or you want check_lockfile to
read the lockfile off disk so a large tree never passes through the model
context.
Hosted, one command:
claude mcp add --transport http lazaretto "https://lazaretto.dev/mcp?ref=npm"
With a key f