Skip to main content
Glama
4DA-Systems

@4da/mcp-server

by 4DA-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to @4da/mcp-server

No user-submitted related servers found.

    Related Servers

    • Security Intel MCP

      datakoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Vulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.
      MIT

    • oss-intel-mcp

      FoundryNet
      A
      license
      Not graded
      quality
      F
      maintenance
      Open source intelligence for AI agents — GitHub project-health scoring, package dependency-risk analysis, trending repositories, license checks, and side-by-side package comparison.
      MIT

    • pkg-intel-mcp

      JanMaa
      F
      license
      A
      quality
      C
      maintenance
      Package intelligence for AI coding agents that checks npm and PyPI package health, deprecation, vulnerabilities, bundle size, and compares alternatives.
      5
      -

    • DepsGuard MCP

      Kim-Kyowon
      A
      license
      A
      quality
      D
      maintenance
      AI-powered dependency vulnerability and breaking change analyzer that scans dependencies, identifies vulnerabilities via OSV.dev, and uses AI to assess real impact and suggest fixes.
      3
      Apache 2.0

    • PatternStack

      patternstack-ai
      A
      license
      B
      quality
      D
      maintenance
      Provides crowdsourced package intelligence and security alerts for AI coding assistants by analyzing project dependencies and framework co-occurrence. It enables automated project scans, package alternative discovery, and data-driven recommendations across multiple programming ecosystems.
      10
      8 npm
      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.9/5.0

    Scored across 9 tools

    Disambiguation3/5

    Some tools are clearly distinct (vulnerability_scan vs dependency_health vs upgrade_planner), but get_context, what_should_i_know, and agent_memory all deal with context/memory and could cause misselection. check_decision_alignment overlaps with decision_memory's 'check' functionality.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern, mixing noun_verb and verb_noun forms (vulnerability_scan, dependency_health, upgrade_planner) with a few verb-first names (get_context, check_decision_alignment). The style is consistent, but verb placement varies slightly.

    Tool Count5/5

    9 tools is appropriate for a developer-assistant server covering security, dependency, and memory features. Each tool seems purposeful and the count is within the ideal 3-15 range.

    Completeness4/5

    The security/dependency workflow is well covered (scan, health, plan), and memory tools cover both recording and recalling. Missing actions like clearing memory or comparing dependency versions are minor gaps that agents could work around.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources