Skip to main content
Glama
Sign In
wikipedia-trends-mcp

wikipedia-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to wikipedia-trends-mcp

No user-submitted related servers found.

    Related Servers

    • Wikipedia Trends API

      trendsapi
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes Wikipedia page view trends as clean JSON, providing normalized 0-100 trend scores, growth rates over 3M/6M/12M/5Y windows, and live most-viewed article feeds, comparable across 15 sources including Google, YouTube, and TikTok.
      MIT

    • wikipedia-trends-mcp

      trendsmcp-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Wikipedia page view trend data including spike detection, historical traffic, and cross-platform comparison, enabling AI to access a leading indicator of public curiosity.
      MIT
    • Trends MCP

      Trends MCPofficial

      trendsapi
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides hosted trend data MCP server for querying Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and 30+ trend sources in natural language from any MCP-compatible AI.
      MIT

    • news-volume-mcp

      trendsmcp-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing news article mention volume data, weekly series, growth percentages, and a live Google News feed as an AI tool.
      20 PyPI
      MIT

    • trend-pulse

      claude-world
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for trend-pulse, an agentic trend intelligence platform that fetches and analyzes trending topics from 37 sources, provides search, historical data, and lifecycle prediction via 29 tools.
      252 PyPI
      64
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: get_growth for point-to-point changes, get_time_series for full history, and get_top_trends for live boards. The descriptions explicitly cross-reference each other to prevent misselection, leaving no ambiguity.

    Naming Consistency5/5

    All three tools follow a consistent 'get_' prefix with a descriptive noun: get_growth, get_time_series, get_top_trends. This predictable pattern makes it easy for agents to infer functionality from names.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped but each tool addresses a fundamental need: growth, historical data, and current trends. This is a well-focused set that avoids redundancy.

    Completeness5/5

    The tools cover the main workflows for a trends service: analyzing growth, retrieving full time series for charting, and accessing live rankings. Edge cases like categories and rank changes are handled, leaving no obvious dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources