FreshRSS MCP Server

The materials explicitly state that no keys or environment variables are required. There is no indication that API keys, access tokens, or system credentials are needed, so credential exposure appears low based on the available information.

The tool is described as interacting with a FreshRSS instance, which normally implies sending requests to a FreshRSS service. Although no fixed host is declared and there is no evidence of exfiltration to unrelated third-party endpoints, this still represents normal network access and the actual target instance should be verified.

The objective checks indicate executes-code, meaning server-side code runs in the local environment. This is common for MCP tools, and the provided materials do not show requests for unusual system privileges or actions clearly unrelated to the stated purpose.

Based on the description, its main data access scope should be subscriptions, articles, and organizational data within FreshRSS. The materials do not state that it reads or writes arbitrary local files, and no overbroad permissions are described, but its ability to read and manage RSS data still warrants checking the actual account scope it can access.

A positive factor is that the project is open source and can be audited. However, it comes from a third-party registry, the repository has no declared license, community adoption is 0 stars, and maintenance status is unknown, so trust and long-term maintenance signals are relatively weak and it is best evaluated in an isolated environment first.