Skip to main content
Glama
bradford-tech

@bradford-tech/npm-package-readme-mcp-server

by bradford-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @bradford-tech/npm-package-readme-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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.
      4 npm
      ISC

    • 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

    • 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
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: searching for packages, retrieving package metadata, and fetching README content. There is no ambiguity between searching and retrieving specific package resources.

    Naming Consistency5/5

    All three tool names follow a consistent verb_noun_from_npm pattern (get_readme, get_package_info, search_packages). The verb choice appropriately reflects each action, and the structure is uniform throughout.

    Tool Count4/5

    Three tools is on the lean side, but the server has a narrow, focused purpose (npm package readme retrieval), so each tool earns its place. The count feels slightly thin rather than excessive or insufficient.

    Completeness4/5

    The core workflow is covered: search for a package, inspect its metadata, then fetch its README. Minor gaps exist, such as fetching version-specific readmes or resolving readmes from alternate sources, but there are no dead ends for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources