Skip to main content
Glama
EbonyLouis

Content Fetcher MCP

by EbonyLouis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Content Fetcher MCP

No user-submitted related servers found.

    Related Servers

    • sSmcp

      bledny1099
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval and analysis of content from YouTube, TikTok, Instagram, and Threads, including metadata, captions, comments, feeds, search results, transcripts, and on-screen text from videos or slides. Supports local stdio and remote HTTP/SSE deployment with optional API keys, Whisper transcription, and Tesseract OCR.
      MIT

    • Kaze Feed

      jackeyfaker77
      A
      license
      A
      quality
      C
      maintenance
      Enables subscribing to RSS/Atom feeds, polling them incrementally, and querying cached entries with search, summaries, and source listings. Tracks per-session consumption state so unacknowledged candidates can be surfaced for proactive notification.
      6
      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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are mostly distinct in purpose: four fetch specific content types (GitHub releases, blog posts, RSS feeds, YouTube videos), while isNewContent and markContentSeen handle content state management. There is minor potential confusion between fetchGooseBlog and fetchRss since both fetch blog posts, but their scopes (specific blog vs. any RSS feed) help differentiate them.

    Naming Consistency2/5

    The naming is inconsistent: fetchGithubReleases, fetchGooseBlog, fetchRss, and fetchYoutube use camelCase with 'fetch' prefix, while isNewContent and markContentSeen use camelCase without a consistent verb pattern. This mix of styles (fetch vs. is/mark) and lack of a uniform naming convention reduces predictability.

    Tool Count5/5

    With 6 tools, the count is well-scoped for a content fetching server. It covers multiple content sources and basic state management, providing a focused set without being overly sparse or bloated, which aligns well with the server's purpose.

    Completeness4/5

    The tool set is largely complete for content fetching and tracking: it includes fetching from various sources (GitHub, blogs, RSS, YouTube) and tools to check and mark content as seen. A minor gap is the lack of a tool to list or manage seen content, but agents can work around this by using isNewContent and markContentSeen in combination.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources