Next free-source huntWe check for new free data every weekday.
Cyber ThreatMCP serverFirst audited Nov 13, 2026

Lazaretto

Supply chain security: free npm lockfile malware check, paid scan of packages, skills, MCP servers.The vendor's description, from its MCP Registry listing.

Passed public checksAudited Nov 13, 2026

Every public check ran and passed. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 296 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
YesSome tools say they can change things. Your AI client should ask you first.
Endpointhttps://lazaretto.dev/mcp

Source code Website Streamable HTTP · protocol 2025-06-18 · server version 1.0.0

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Note: 5 tools are labelled as able to change things.

    Expected for tools that send, write or buy. Your AI client should ask before calling them.

    • scan_artifact
    • scan_lockfile_deep
    • scan_mcp_server
    • check_mcp_tools
    • get_free_key
  • Passed: Every tool says whether it only reads or can change things.

Tools

  • Passed: 10 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Note: Protocol version 2025-06-18.

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (10)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • known_bad_lookupCheck a SHA-256 against Lazaretto's known-bad indicator set (refreshed daily from abuse.ch). Free and anonymous. A miss only means this exact hash is not in the indicator set; it is not a clean verdi…Read-only
  • check_lockfileCheck EXACTLY-PINNED npm dependencies against published malicious-package advisories (OSV/OpenSSF). Free, anonymous, one call for the whole set. Give EITHER `lockfile`, the full text of a package-loc…Read-only
  • scan_artifactDeterministically analyze a package, repo, AI model, skill, or file for malicious behavior (credential theft, data exfiltration, obfuscation, prompt injection aimed at the agent, install scripts, mod…Can change things
  • scan_lockfile_deepBehaviorally scan the exactly-pinned dependencies in a lockfile, not just their identities: reads the code of each package and screens for credential theft, exfiltration, obfuscation, prompt injectio…Can change things
  • scan_mcp_serverCheck an MCP server BEFORE you connect to it. Asks the server to introduce itself and list its tools, then analyzes the text it hands an agent: tool names, descriptions, parameter schemas and server…Can change things
  • check_mcp_toolsCheck tool definitions you ALREADY HOLD, with no network call to anyone. Most MCP servers run locally over stdio and have no endpoint that can be reached, so this is the only way to check them, and y…Can change things
  • find_mcp_serversFind an MCP server for a job, free and with no key: describe what you need ("postgres", "send slack messages", "browser automation") and get matching servers from the official MCP registry, each with…Read-only
  • find_attestationAsk whether anyone has already attested an artifact, BEFORE you install it or pay to scan it. Free and anonymous. Give a package identity like "chalk@5.6.1", an MCP server endpoint URL, or a sha256 c…Read-only
  • verify_attestationVerify a Lazaretto scan attestation that another agent (or a README, or a lockfile) handed you, WITHOUT re-scanning or paying. Free and anonymous. Returns signature validity and the signed claims, in…Read-only
  • get_free_keyGet a free developer key for the metered tools on this server, without leaving this session. No payment, no account, no card. The key holds a small daily allowance that refills every day, and one cre…Can change things

Audit history

  1. Nov 13Passed

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200296 ms
initializedHTTP 20258 ms
tools/listHTTP 200121 ms
unknown-methodHTTP 20066 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.