Skip to main content
Glama
crunchtools

mcp-feed-reader-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mcp-feed-reader-crunchtools

No user-submitted related servers found.

    Related Servers

    • rss-mcp

      bartosz-kuc
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server for reading and searching RSS and Atom feeds, enabling AI assistants to fetch feed contents, search entries by keyword, and view feed metadata without any cloud intermediary.
      3
      MIT

    • simply-feed-mcp

      hmmroger
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for managing and querying RSS/news feeds, enabling real-time fetching, searching, and retrieval of feed items.
      5
      7 npm
      1
      MIT
    • @missionsquad/mcp-rss by MissionSquad

      @missionsquad/mcp-rssofficial

      MissionSquad
      A
      license
      B
      quality
      C
      maintenance
      MCP server for fetching, parsing, and managing RSS feeds. Features Fetch and parse RSS/Atom feeds In-memory caching with TTL Batch fetching of multiple feeds Monitor feeds for new items Search content across multiple feeds Extract and format feed content
      6
      43 npm
      12
      Apache 2.0

    • news-mcp

      runawaydevil
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for RSS news aggregation, providing tools to list sources, fetch latest news, search articles, and get stats. It stores feeds in SQLite and supports local/Docker deployment with bearer token or OAuth authentication.
      -
    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.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: feed CRUD, entry listing/reading/searching, read-state toggles, category management, stats, and OPML import/export. The only minor overlap is read_entry_tool auto-marking entries as read, but its primary purpose (content retrieval) is clearly distinct from mark_read_tool's explicit state change. No two tools are confusable.

    Naming Consistency5/5

    All 17 tools use consistent snake_case with a uniform verb_noun_tool pattern (e.g., add_feed_tool, delete_category_tool, list_entries_tool). The redundant '_tool' suffix is applied uniformly, so there is no mixing of conventions. The pattern is entirely predictable.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 sweet spot, but each tool serves a clear purpose in a full-featured feed reader: feed management, entry handling, category CRUD, stats, and OPML support. The set feels well-scoped rather than bloated.

    Completeness4/5

    The surface covers most feed-reader workflows: add/delete/list/get feeds, refresh, entry listing/reading/searching, read-state toggles, category CRUD, stats, and OPML import/export. The notable gap is an update_feed operation (e.g., changing URL, title, or category assignment); workarounds exist (delete and re-add) but lose state. This is a minor gap rather than a critical failure.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources