Skip to main content
Glama
lazaretto-mcp

lazaretto-mcp

Related Servers

Alternatives to lazaretto-mcp

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A ready-to-deploy MCP server with in-process agent verification via KYA-OS Checkpoint, enabling secure tool access for verified agents.
    1
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    An MCP server that enforces agent persona permissions by acting as a gateway, scoping tool access and denying unauthorized capabilities.
    11 npm
    7
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that enables AI coding agents to pre-validate packages before installation, audit code changes for duplicated boilerplate and lazy placeholders, and detect when modified files drift from the original task intent.
    67 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    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

TDQS

A4.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct input type and question: hash vs lockfile vs single artifact vs whole tree vs live MCP endpoint vs pasted tool JSON vs attestation lookup vs token verification. Descriptions also cross-reference the alternatives in 'prefer X when' language, so even the near-pairs (check_lockfile/scan_lockfile_deep, scan_mcp_server/check_mcp_tools, find_attestation/verify_attestation) have crisp boundaries.

Naming Consistency4/5

Names are mostly verb_noun (check_lockfile, scan_artifact, scan_mcp_server, find_attestation, verify_attestation, check_mcp_tools) with a consistent semantic split between free 'check' and paid 'scan'. Minor deviations: known_bad_lookup inverts the order, and the scan/check prefix choice is meaningful but not spelled out as a rule.

Tool Count5/5

Eight tools is well-scoped: one per input type and trust question, with no redundant entries. Every tool has a plausible caller and the free/paid tiering justifies the parallel pairs rather than duplicating them.

Completeness4/5

The surface covers the core lifecycle: cheap checks first (hash, lockfile identity, attestation lookup), paid behavioral scans (single artifact, whole tree, live server, pasted tool set), plus attestation verification. Minor gaps: no tool to query account/credit balance or corpus/rules version, and no batch scan of multiple individual artifacts outside a lockfile.

Maintenance

ActivityMaintained
ResponsivenessUsually handled