RSS Feed Reader: Atom Feed and JSON Feed in One List

io.github.bepolabsPublished by GitHub account bepolabsv1.0.0Updated Nov 12, 2026

Turn RSS, Atom and JSON Feed sources into one deduplicated dataset.

The publisher's own server: Atom.com — Premium Domains

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote Apify-hosted MCP server that turns RSS, Atom and JSON Feed sources into one deduplicated dataset an assistant can work with.

What you can do
  • Collect entries from RSS, Atom and JSON Feed sources.
  • Merge multiple feeds into a single deduplicated dataset.
  • No individual tools are listed in the manifest, so the exact operations are not documented; the description only covers feed aggregation into one dataset.
When to use it
Useful when you want an assistant to gather news or blog items from several feeds and work from one combined, duplicate-free list instead of checking each feed separately.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: either an Apify API token sent in the Authorization header as a Bearer token, or sign-in through OAuth.
Before you install
An Apify API token is a credential that may carry account access and usage costs on the Apify platform; prefer OAuth sign-in where possible and keep the token out of shared configuration. Feed content is fetched through Apify's hosted service, so the feed URLs you supply are sent to that third party.

Installation

In SourceWeft

  1. Open RSS Feed Reader: Atom Feed and JSON Feed in One List in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bepolabs%2Frss-reader/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rss-feed-reader-atom-feed-and-json-feed": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bepolabs/rss-reader"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 12, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Atom integrations