Skip to main content
Glama
jamesdfinance-dev

lazaretto-mcp

by jamesdfinance-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to lazaretto-mcp

No user-submitted related servers found.

    Related Servers

    • KYA-OS MCP Server by kya-os

      KYA-OS MCP Serverofficial

      kya-os
      F
      license
      Not graded
      quality
      C
      maintenance
      A ready-to-deploy MCP server with in-process agent verification via KYA-OS Checkpoint, enabling secure tool access for verified agents.
      1
      -
    • Outfit by MyceliumInc

      Outfitofficial

      MyceliumInc
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces agent persona permissions by acting as a gateway, scoping tool access and denying unauthorized capabilities.
      10 npm
      7
      MIT

    • impact-preview

      agent-polis
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides impact preview and approval workflow for AI agent actions, allowing users to see diffs and risk assessments before any changes are executed.
      1
      MIT

    • velvet-rope

      paulchum
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for agent authorization that tests the full effect surface and enforces control over consequential actions before dispatch, emitting verifiable execution evidence.
      2
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct use case: check_lockfile for lockfile dependency trees, known_bad_lookup for individual hashes, and scan_artifact for behavioral analysis. Descriptions explicitly state when to prefer each, eliminating ambiguity.

    Naming Consistency4/5

    Most tools follow verb_noun pattern (check_lockfile, scan_artifact), but known_bad_lookup is a noun phrase. This minor inconsistency slightly reduces coherence, but names are still clear and descriptive.

    Tool Count5/5

    Three tools cover the core security analysis domain (dependency scanning, hash lookup, artifact analysis) without overlap or missing functionality. The count is well-scoped for the server's purpose.

    Completeness5/5

    The set provides a complete lifecycle for assessing malicious packages: broad lockfile scan, precise hash check, and deep behavioral analysis. No obvious gaps exist for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources