Skip to main content
Glama
mrfentmen

artifact-gauge-mcp

by mrfentmen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to artifact-gauge-mcp

No user-submitted related servers found.

    Related Servers

    • Maven Decoder MCP Server

      salitaba
      A
      license
      B
      quality
      A
      maintenance
      A comprehensive MCP server for analyzing Maven jar files in the local repository, enabling AI agents to understand dependencies, analyze bytecode, and extract source code.
      17
      345 npm
      197 PyPI
      20
      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
      -
    • Euthynos by euthynos-org

      Euthynosofficial

      euthynos-org
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, read-only MCP server that provides AI coding agents with structural evidence about a repository, including dependency analysis and impact assessment, while naming the boundary of every answer without any LLM calls.
      44 npm
      Apache 2.0
    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.7/5.0

    Scored across 2 tools

    Disambiguation4/5

    Both tools involve inspection, but inspect_artifacts provides a broad overview of artifact sizes and extensions, while inspect_manifest targets a single dependency manifest. The scope difference is clear, though the shared 'inspect' prefix could cause minor confusion.

    Naming Consistency5/5

    Both tools use a consistent verb_noun pattern (inspect_artifacts, inspect_manifest), making their purposes predictable and the naming style uniform.

    Tool Count3/5

    With only two tools, the server feels minimal and borderline for a meaningful tool set. However, the two tools cover different granularities, making the count somewhat reasonable for a focused inspection-only purpose.

    Completeness4/5

    The tools cover the main inspection needs: a high-level artifact overview and detailed single-manifest metadata. There may be gaps like per-file detail inspection, but within the stated non-invasive inspection scope, the surface is fairly complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources