Skip to main content
Glama
4DA-Systems

@4da/mcp-server

Official

Related Servers

Alternatives to @4da/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.
      5
      95 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to run sub-millisecond, fully offline CVE lookups and audit dependency manifests such as requirements.txt and package.json against known vulnerable version ranges. It returns CVSS severity details and calculates the minimal safe upgrade version needed to eliminate matching vulnerabilities, without rate limits or API keys.
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
      14
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables autonomous AI agents and CI/CD runners to discover repository modules, scan outdated dependencies, fetch version histories, and apply verified dependency updates with major-version safety guardrails across polyglot monorepos.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.
      4,912 npm
      4
      MIT

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation3/5

    Several tools overlap in purpose: vulnerability_scan, dependency_health, and dependency_check all report vulnerabilities/CVE status, upgrade_impact and upgrade_planner both concern upgrades, and get_context vs what_should_i_know vs check_decision_alignment all answer 'what do I know about this project/user.' The detailed 'call BEFORE' triggers in descriptions mitigate the confusion, but an agent still faces multiple plausible choices for a security or upgrade question.

    Naming Consistency4/5

    All names use snake_case consistently. Verb styles vary (verb_noun like check_decision_alignment, bare verbs like vulnerability_scan, pure nouns like dependency_health, and a phrase like what_should_i_know), which is readable but not a single predictable pattern.

    Tool Count4/5

    11 tools is a reasonable scope for a dependency/context advisor, and each maps to a distinct workflow stage. The set is slightly padded by overlapping advisory tools (what_should_i_know vs get_context) but nothing is gratuitous.

    Completeness4/5

    Coverage is broad: decisions (record/list/update/supersede), memory (store/recall), vulnerability scanning, version safety checks, upgrade impact and planning, and ecosystem news. Gaps are minor—no explicit tool to enumerate projects or export/clear memory—but core lifecycle workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive