Skip to main content
Glama
zcag

npm-search-mcp

by zcag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to npm-search-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
      34 npm
      MIT

    • 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

    • versionator-mcp

      trianglegrrl
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that queries 19 package registries (npm, PyPI, crates.io, etc.) to retrieve the latest version of packages and their metadata.
      21
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clear, distinct purpose: searching for packages, fetching details of a specific package, and comparing alternatives. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_packages, get_package, compare_packages. The pattern is uniform and predictable.

    Tool Count4/5

    With only 3 tools, the server is well-scoped for its purpose. Each tool is essential and non-redundant, though the count is on the lower end of the ideal range.

    Completeness4/5

    The tool set covers the core workflow of discovering and evaluating npm packages. Minor gaps include lack of package version history or no ability to get all versions, but the primary workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources