Skip to main content
Glama
TweedBeetle

dependency-fitness-mcp

by TweedBeetle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dependency-fitness-mcp

No user-submitted related servers found.

    Related Servers

    • npm-registry-mcp

      howmanysmall
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for searching, inspecting, and evaluating NPM packages through health scoring and license risk assessments. It provides comprehensive package analysis including maintenance status, popularity trends, and security vulnerability reports to help users make informed dependency decisions.
      3
      MIT

    • freshdeps-mcp

      SolvoHQ
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that checks npm and PyPI package health, providing maintenance signals, version info, CVE counts, and alternative suggestions.
      MIT

    • pkg-oracle

      julian-martin89
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that verifies npm and PyPI packages before installation, checking for existence, known vulnerabilities, OpenSSF scorecard, and typosquatting, returning an ALLOW/WARN/BLOCK verdict.
      MIT

    • dependency-health

      NY5184
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that performs comprehensive health checks on project dependencies for JavaScript and Python projects, detecting outdated packages and fetching changelogs.
      1
      -
    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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one checks a single package with cross-validated intelligence, the other audits multiple dependencies at once with a summary. No ambiguity between them.

    Naming Consistency4/5

    Both tools follow a verb_noun pattern (check_package_fitness, audit_dependencies) but use different verbs ('check' vs 'audit') and different objects. Slightly inconsistent but still predictable.

    Tool Count4/5

    With only 2 tools, the server is lean but covers the core functionality (single package check and batch audit). Could be expanded with more granular tools, but the count is reasonable for the narrow domain.

    Completeness4/5

    The server provides the main operations needed for npm dependency health checking: single-package verdict and batch audit. Lacks features like vulnerability details or update commands, but covers the essential use cases without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources