Skip to main content
Glama

Related Servers

Alternatives to Hound MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.
      15
      98 npm
      15
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Gives AI coding agents on-demand security playbooks, a code scanner they can run on their own output, and live lookups against CISA KEV, NVD and OSV so they verify threats instead of guessing. Runs locally with no API keys or accounts, exposing skills, tools and a secure-build prompt to Claude Code, Codex, Cursor or any MCP client.
      13
      Apache 2.0
    • A
      license
      C
      quality
      D
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.
      78 npm
      MIT

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: e.g., advisories for details, audit for lockfile scanning, compare for side-by-side, inspect for profile, license_check for compliance, popular for scanning popular packages, preinstall for safety check, score for computation, tree for dependencies, typosquat for name similarity, upgrade for safe version, vulns for listing. No overlap.

    Naming Consistency5/5

    All tools follow the 'hound_' prefix with a descriptive noun or verb-noun compound (e.g., audit, compare, license_check, preinstall, score, tree, typosquat, upgrade, vulns). The pattern is consistent and predictable, aiding agent selection.

    Tool Count5/5

    12 tools cover the domain of package security and dependency analysis comprehensively without being excessive. Each tool serves a necessary function, and the count is appropriate for the scope.

    Completeness5/5

    The tool set covers the full lifecycle: advisory retrieval, vulnerability scanning (lockfiles), profiling, comparison, license checking, popular package scanning, pre-install checks, scoring, dependency trees, typosquat detection, upgrade recommendations, and vulnerability listing. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessSlow