Back to Browse

Feedport MCP Server

Developer ToolsModerate5.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

Fetch and parse RSS or Atom feeds from a URL.

About

Fetch and parse RSS or Atom feeds from a URL.

Security Report

5.6
Moderate5.6Moderate Risk

feedport is a small RSS/Atom reader that fetches a caller-supplied URL and returns parsed feed fields, with no shell execution, filesystem access, credential handling, or exfiltration patterns found. The main concerns are low-severity: the server will fetch any URL it is given, including internal addresses, and it applies no response size or timeout limits. Permissions match its purpose, so the score remains high. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-feedport": {
      "args": [
        "-y",
        "@reneturcios/feedport"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

feedport

feedport reads web feeds for you. Give it the address of an RSS 2.0 or Atom document and it hands back the feed's title, link and description plus a clean list of its items — titles, links, descriptions, dates and ids — without you having to look at raw XML. It can also check an address first and tell you whether what lives there really is a feed.

Install

npx @reneturcios/feedport validate-feed https://example.com/feed.xml

Or run the container image:

docker run -i ghcr.io/cloudcorprecords/feedport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

All commands print JSON.

# Whole feed: channel metadata plus items
feedport fetch-feed https://example.com/feed.xml

# Just the items, at most five of them
feedport fetch-feed-items https://example.com/feed.xml --limit 5

# Is this address actually a feed?
feedport validate-feed https://example.com/feed.xml
# {"valid": true, "format": "rss", "item_count": 12}

feedport --version

Exit codes: 0 on success, 1 when a feed cannot be fetched or parsed (the error names the problem), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

npx -y @reneturcios/feedport mcp

MCP client configuration:

{
  "mcpServers": {
    "feedport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/feedport", "mcp"]
    }
  }
}

Tools

ToolInputWhat it returns
fetch_feedurl (string, required), limit (integer, optional)The feed's title, link and description, plus items — each with title, link, and description, pubDate and guid when the document carries them.
fetch_feed_itemsurl (string, required), limit (integer, optional)Only the item list, in the same shape as fetch_feed's items.
validate_feedurl (string, required)valid, the detected format (rss, atom or unknown), the item_count, and an error string when the address is not a usable feed.

RSS 2.0 items come from <item> elements and Atom entries from <entry> elements; for Atom, an entry's summary (or content) becomes its description, its published (or updated) date becomes pubDate, and its id becomes guid. CDATA sections and XML entities are decoded.

Development

npm install
npm run build   # tsc -> dist/
npm test        # node test runner over test/*.test.ts, no network
npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!