lazaretto-mcp
Related Servers
Alternatives to lazaretto-mcp
- MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides tools to query the official MCP Registry.445 npm3MIT
- AlicenseAqualityCmaintenanceMCP server that searches npm packages and returns live registry data without an API key. Supports package search, detailed info, and side-by-side comparison of packages.341 npmMIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents search, view, install, and validate skills from the skillhub registry through tool calls.MIT

KYA-OS MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceA ready-to-deploy MCP server with in-process agent verification via KYA-OS Checkpoint, enabling secure tool access for verified agents.1MIT- AlicenseNot gradedqualityDmaintenanceMCP server for managing AI agent skills with pre-flight compatibility checks, ensuring missing dependencies are detected before execution.84MIT

Outfitofficial
AlicenseNot gradedqualityFmaintenanceAn MCP server that enforces agent persona permissions by acting as a gateway, scoping tool access and denying unauthorized capabilities.11 npm7MIT- AlicenseNot gradedqualityBmaintenanceAn 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 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP 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.1MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.