Skip to main content
Glama
verdaccio

@verdaccio/mcp-server

Official
by verdaccio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @verdaccio/mcp-server

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
      43 npm
      MIT

    • npm-mcp

      rajeshn95
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for the public npm registry that enables AI clients to search for npm packages and retrieve focused package metadata, versions, and latest dist-tags without exposing install or publish capabilities.
      5 npm
      ISC

    • ts-docs-mcp

      xvantz
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
      1
      8 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource+action: package lifecycle (publish/unpublish/get/find), registry lifecycle (start_registry), user auth (add_user/login/get_profile), and token management (list/create/delete). The only near-neighbors, add_user vs login and find_package vs get_package, are differentiated by register-vs-authenticate and search-vs-detail respectively.

    Naming Consistency4/5

    Nearly all tools follow a clean snake_case verb_noun pattern (publish_package, create_token, get_profile). The single-verb 'login' is a minor deviation from the verb_noun convention but is still readable and unambiguous.

    Tool Count5/5

    11 tools sit comfortably in the well-scoped 3-15 range and each maps to a needed registry operation. No redundant or filler tools are present.

    Completeness4/5

    Covers the main registry workflows: publish/unpublish, discovery, authentication, and full token CRUD. Minor gaps exist (no whole-package removal or metadata update beyond publish, no logout), but these are workable rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources