RSS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIORITY_RSSHUB_INSTANCE | No | A preferred RSSHub instance URL that will be placed at the top of the polling list |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_feedB | Get RSS feed from any URL, including RSSHub feeds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect by default.
The single tool name 'get_feed' follows a clear verb_noun pattern, and with no other tools, consistency is inherently perfect.
One tool is too few for a typical RSS server, which would benefit from operations like list_feeds, add_feed, or refresh_feeds, making the scope feel incomplete.
The tool only allows fetching a feed from a URL, lacking essential RSS functionalities such as managing subscriptions, updating feeds, or parsing feed content, resulting in significant gaps.