Skip to main content
Glama
trendsmcp-ai

npm-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to npm-trends-mcp

No user-submitted related servers found.

    Related Servers

    • pkg-peep

      chris-trag
      A
      license
      B
      quality
      D
      maintenance
      Enables querying NPM package download statistics, metadata, and dependency information through natural language.
      2
      MIT

    • npmlens-mcp

      rakeshmenon
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to search the npm registry and retrieve package metadata, READMEs, download stats, GitHub details, and usage snippets via the Model Context Protocol.
      9
      5 npm
      MIT

    • NPM Context Agent MCP

      JuanSebastianGB
      A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive contextual information about npm packages including README files, versions, dependencies, download statistics, and search functionality. Enables users to explore and analyze npm packages through natural language queries with intelligent GitHub README fetching and branch fallback.
      9
      MIT

    • mcp-npm

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

    • package-intel-mcp

      datakoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.
      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

    A4.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are largely distinct: get_top_trends targets live boards, while get_growth and get_time_series both handle historical keyword data and could be confused. However, the descriptions explicitly separate 'point-to-point growth' from 'full historical series' and tell agents which to prefer, so the boundary is workable.

    Naming Consistency5/5

    All three tools follow a clean get_<noun> pattern: get_growth, get_top_trends, get_time_series. There is no mixing of styles or inconsistent verbs, making the naming predictable and easy to navigate.

    Tool Count5/5

    Three tools is a focused, sensible scope for a trends data server. Each tool covers a distinct core user need: current top boards, point-to-point growth, and full time-series data, so each earns its place.

    Completeness4/5

    The set covers the main trend-related workflows: live rankings, growth comparisons, and historical charting data. Minor gaps exist, such as no explicit endpoint for listing available feeds, categories, or discovering keywords, but agents can work around those with known values and guidance in the descriptions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources