Skip to main content
Glama
santoshyadavdev

e18e-module-replacements-mcp

by santoshyadavdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to e18e-module-replacements-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-npm-tools

      rog0x
      A
      license
      A
      quality
      D
      maintenance
      MCP server providing npm registry search, package details, dependency auditing, bundle size estimation, and package comparison tools for AI agents.
      5
      27 npm
      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

    • mcp-dep-tools

      rog0x
      A
      license
      A
      quality
      D
      maintenance
      MCP server providing dependency and package management tools for AI agents. Analyze licenses, find outdated packages, visualize dependency trees, estimate bundle sizes, and audit security vulnerabilities.
      5
      32 npm
      MIT

    • ts-docs-mcp

      xvantz
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
      1
      23 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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: lookup_replacement searches for a specific module replacement, while scan_dependencies processes a list of dependencies. No ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern using snake_case: lookup_replacement and scan_dependencies. The naming is predictable and uniform.

    Tool Count3/5

    With only 2 tools, the surface is thin for the domain of module replacements. While the tools cover individual lookup and bulk scanning, the count is at the lower boundary of reasonable scope.

    Completeness4/5

    The tools cover the two main use cases: searching for a single replacement and scanning a dependency list. A minor gap is the lack of a tool to list all possible replacements, but the core functionality is present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources