crypto-rss-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_rss_feedA | |
| get_crypto_rss_listA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_rss_feed | Create a prompt for analyzing RSS feed content. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves a list of available RSS feeds, while the other fetches content from a specific RSS feed. There is no overlap in functionality, and the descriptions make their unique roles explicit.
Both tools follow a consistent verb_noun pattern with 'get_' prefixes (get_crypto_rss_list and get_rss_feed). This naming scheme is predictable and aligns well with their actions, making them easy to distinguish and use.
With only two tools, the server feels thin for its domain of cryptocurrency RSS feeds. While the tools cover basic retrieval, the lack of operations like filtering, updating, or managing feeds limits functionality and suggests an incomplete surface for typical RSS workflows.
The server is severely incomplete for handling cryptocurrency RSS feeds. It lacks essential operations such as adding, updating, or deleting feeds, as well as advanced features like search, categorization, or subscription management. This minimal set will likely cause agent failures in more complex tasks.