Skip to main content
Glama
Sign In
DepShield MCP

DepShield MCP

by devanshkaria88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DepShield MCP

No user-submitted related servers found.

    Related Servers

    • depscope-mcp

      cuttalo
      A
      license
      Not graded
      quality
      D
      maintenance
      Validates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.
      55 npm
      AGPL 3.0

    • aftertaste

      WiseeCarrot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to scan projects or changed files for risky leftovers like hallucinated packages, exposed secrets, truncated code, and unfinished stubs, and to verify that packages exist before installing them.
      27 npm
      MIT

    • pkgbouncer

      rayan1810
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.
      360 npm
      MIT

    • vetgate

      techdevfun
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to check npm packages, GitHub Action refs, and remote scripts before execution, returning deterministic ALLOW/DENY/REVIEW verdicts with evidence and a re-checkable manifest.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are generally distinct with clear boundaries: audit_project targets manifest files, check_dependency is for pre-install validation, check_npm_health focuses on maintenance metrics, and deep_scan examines transitive dependencies. Minor overlap exists between check_dependency and check_npm_health (both examine single packages), but their purposes (security vs health) are different enough to guide selection.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (audit_project, check_dependency, find_safe_version, get_advisory_detail, suggest_alternative). However, 'deep_scan' breaks the convention by using an adjective_noun structure rather than a verb-led name like 'scan_dependencies' or 'analyze_transitive_deps'. 'check_npm_health' is consistent but domain-specific (npm) while others are generic.

    Tool Count5/5

    Seven tools is an ideal count for this domain. The set covers the full workflow: project scanning (audit_project), package vetting (check_dependency, check_npm_health, deep_scan), remediation (find_safe_version, suggest_alternative), and investigation (get_advisory_detail). No tool feels redundant or filler.

    Completeness4/5

    Strong coverage of the dependency security lifecycle including vulnerability detection, health assessment, transitive dependency analysis, and remediation strategies. Minor gaps include the lack of an 'apply_fix' or 'update_manifest' tool to automatically remediate findings, and no SBOM generation capability, but agents can work around these with the existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources