Skip to main content
Glama
lpm-dev

@lpm-registry/mcp-server

Official
by lpm-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @lpm-registry/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
      27 npm
      MIT

    • PawnDex MCP Server

      sittiev
      A
      license
      A
      quality
      D
      maintenance
      MCP server for the Pawn package index, enabling AI assistants to search and inspect Pawn packages, retrieve repository details, and view ecosystem statistics.
      4
      1
      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
    • MCPfinder by mcpfinder

      MCPfinderofficial

      mcpfinder
      A
      license
      Not graded
      quality
      B
      maintenance
      AI-first MCP server discovery tool that enables agents to search, inspect, and install MCP servers from multiple registries.
      12
      AGPL 3.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

    A4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: package management, information retrieval, search, user/owner operations, etc. Overlapping tools like lpm_api_docs, lpm_llm_context, and lpm_package_context are well-differentiated by the specific type of information they provide, and descriptions clearly state when to use each.

    Naming Consistency5/5

    All tools follow a consistent 'lpm_verb_noun' pattern using lowercase snake_case (e.g., lpm_add, lpm_api_docs, lpm_search_owners). Naming is predictable and makes it easy to infer a tool's function from its name.

    Tool Count5/5

    17 tools is well-scoped for a package registry server, covering the full workflow: discovery (search, info, docs), installation (add, install, audit), usage (browse_source, package_skills), and administrative actions (user_info, pool_stats). Each tool earns its place.

    Completeness5/5

    The tool surface is comprehensive for LPM registry operations, including search, package metadata, installation methods, source browsing, auditing, documentation, user/owner info, marketplace info, and pool earnings. No obvious gaps for common tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources