Skip to main content
Glama
jackeyfaker77

Kaze Feed

by jackeyfaker77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Kaze Feed

No user-submitted related servers found.

    Related Servers

    • Feedkeeper MCP Server

      visualfusion
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients like Claude to subscribe to RSS/Atom feeds, list feeds with unread counts, fetch and search new items, and mark items as read, all scoped to the authenticated user's account.
      1,334 npm
      1
      MIT

    • feedkit

      ArkNill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to search a curated RSS/Atom catalog, subscribe to and collect feeds, and query collected articles through natural-language tools.
      2
      MIT

    • mcp-feeds

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to list, read, and fetch RSS/Atom feeds, with curated categories and robust fetching capabilities.
      2 npm
      MIT

    • FeedWatch MCP

      bruceonline2026
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to register RSS/Atom/JSON Feed URLs and be alerted when their content changes, including in-place edits to existing items that produce no new entry. It reports field-level diffs (what field changed, from what to what) and pushes HMAC-signed webhook notifications, with SSRF protection and retry handling.
      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.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct phase of the feed lifecycle: manage subscriptions, query cache, poll sources, read proactive events, acknowledge events, and check status. Slight overlap exists between feed_query (latest) and get_proactive_events for reading content, but the consumer/session_key workflow and explicit no-collect/no-send semantics differentiate them.

    Naming Consistency3/5

    All names use snake_case, but the prefix/style is mixed: feed_manage, feed_query, and feed_status use a noun-first pattern, while poll_feeds, get_proactive_events, and acknowledge_events are verb-first. The set is readable but lacks a single predictable convention.

    Tool Count5/5

    Six tools is well-scoped for an RSS/Atom feed and event-consumption server. Each tool has a clear, non-redundant purpose, and no tool feels trivial or out of place.

    Completeness4/5

    The surface covers subscription CRUD (subscribe, list, unsubscribe, pause, resume), polling, querying cached content, proactive event retrieval, acknowledgement, and status. Minor gaps exist, such as fetching a single event by ID or bulk acknowledgement, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources