Skip to main content
Glama
YawLabs

@yawlabs/npmjs-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yawlabs/npmjs-mcp

No user-submitted related servers found.

    Related Servers

    • @mgcrea/mcp-npm

      mgcrea
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with the npm registry, covering package intel, dist-tags, trusted publisher configuration, access and team governance, tokens, security advisories, and publishing, with read-only tools by default.
      3
      157 npm
      MIT

    • mcp-npm

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching npm packages, retrieving package details and version histories, and fetching download statistics through the npm Registry API.
      1 npm
      MIT

    • npm-registry-mcp

      vinkius-labs
      F
      license
      Not graded
      quality
      D
      maintenance
      Grants AI agents real-time access to the NPM registry, enabling package metadata retrieval, version checks, and dependency auditing for up-to-date code generation.
      7 npm
      3
      -

    • pkg-booper

      FennecOnTheNet
      A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with tools to check npm package versions and security heuristics, including version lookups, signal-based analysis, and batch analysis of package.json files.
      5
      6 npm
      AGPL 3.0

    • 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
      25 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 64 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear boundaries between metadata, downloads, security, teams, and hooks. A few auth-focused tools (npm_whoami, npm_profile, npm_verify_token, npm_check_auth) and download variants (npm_downloads, npm_downloads_range, npm_downloads_bulk) could be confused, but the descriptions help disambiguate them.

    Naming Consistency4/5

    The npm_ prefix and snake_case are consistent, and most tools follow a resource-first pattern (npm_team_create, npm_hook_add, npm_dist_tag_set). However, a handful of action-first verbs (npm_search, npm_compare, npm_audit) and bare nouns (npm_health, npm_tokens) break the pattern, creating minor inconsistency.

    Tool Count2/5

    64 tools is far beyond the well-scoped 3-15 range. Even for the broad npm registry API, this is excessive; an agent must parse many near-synonymous entries, and several groups (downloads variants, auth checks, team management) could be consolidated into fewer, more parameterized tools.

    Completeness4/5

    The server covers most of the npm registry domain: metadata, search, downloads, security, auth, teams, orgs, hooks, dist-tags, and unpublishing. The main gap is the absence of an actual npm_publish tool (only npm_publish_preflight exists), and token creation is deliberately omitted, so publishing workflows require a human handoff.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources