Skip to main content
Glama
4DA-Systems

@4da/mcp-server

Official
by 4DA-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @4da/mcp-server

No user-submitted related servers found.

    Related Servers

    • upgrade-pilot-mcp

      kdinisv
      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
      35 npm
      MIT

    • Elevate

      DennisRepa
      A
      license
      Not graded
      quality
      B
      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.
      390 npm
      MIT

    • Weavatrix

      Weavatrix
      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

    • agent-versions

      AndrewTtofi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    The dependency tools (vulnerability_scan, dependency_health, upgrade_planner, upgrade_impact, dependency_check) each have distinct triggers and outputs, but they cluster tightly around the same CVE/version domain and could be confused at the edges. The memory tools (decision_memory, agent_memory, check_decision_alignment) overlap more noticeably, since agent_memory explicitly also stores decisions that decision_memory owns.

    Naming Consistency3/5

    Most names are snake_case noun phrases (vulnerability_scan, dependency_health, upgrade_planner, decision_memory), but the set mixes noun-phrase and verb_noun styles (get_context, check_decision_alignment) and includes the outlier 'what_should_i_know'. Readable, but no single predictable pattern.

    Tool Count5/5

    11 tools is well-scoped for a dependency-intelligence and memory assistant, and each tool appears to earn its place with a defined workflow role (pre-task briefing, scanning, planning, impact, memory).

    Completeness4/5

    Coverage spans scanning, health, planning, impact, decisions, and cross-agent memory, which is strong for the stated domain. Minor gaps: no tool to enumerate the project's declared dependencies/manifests directly, and no way to record or apply the upgrade outcome after planning.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources