Skip to main content
Glama
enesjakozh
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

RSS3 的 MCP 服务器

集成 RSS3 API 的 MCP 服务器实现。轻松查询开放 Web。

特征

https://docs.rss3.io/guide/developer/api中的任何内容。

例如，

  • 查询去中心化链和平台上的数据；

  • 在社交媒体平台上查询数据；

  • 查询 RSS3 网络上的数据（关于权益、节点等）；

  • 查询人工智能情报。

  • ...

示例

vitalik 最近做了什么？

示例响应

能告诉我有关最近的人工智能情报吗？

示例响应

给我看看 ID 为 2048 的 rss3 芯片

示例响应

最适合质押的 rss3 节点是什么？

示例响应

Related MCP server: MCP-RSS-Crawler

用法

与 Claude Desktop 一起使用

将其添加到您的claude_desktop_config.json中：

{
  "mcpServers": {
    "rss3": {
      "command": "npx",
      "args": [
        "mcp-server-rss3"
      ]
    }
  }
}

与游标一起使用

  1. 打开设置 -> 光标设置

  2. 点击“MCP”

  3. 使用以下命令添加新的 MCP 服务器：

{
  "mcpServers": {
    "rss3": {
      "command": "npx",
      "args": [
        "mcp-server-rss3"
      ]
    }
  }
}

与 ChatWise 一起使用

  1. 打开“设置”->“工具”

  2. 使用此命令添加新工具：

npx mcp-server-rss3

Available Tools

1 tool
API-get-input-schemaA

Get the input schema for a given API. We should always use this tool to get the input schema for a given API before calling the API.

ParametersJSON Schema
NameRequiredDescriptionDefault
toolNameNoThe name of the tool to get the input schema for

TDQS

A4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and description does not disclose behavioral traits such as read-only nature, authentication needs, or side effects. While the action implies no side effects, the description fails to explicitly state any behavioral constraints beyond the basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, no redundant information. Purpose is front-loaded in the first sentence. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description adequately covers its purpose and usage. However, it does not describe the output format or return value, which would be useful for an agent invoking this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter 'toolName', with a clear description. The tool description adds no additional meaning beyond what the schema already provides, meeting baseline expectations but not exceeding them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it gets the input schema for a given API and emphasizes using it before calling the API. Verb and resource are specific. No sibling tools to differentiate, but purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'always use this tool to get the input schema... before calling the API.' Provides clear when-to-use guidance. No alternatives or exclusions needed due to absence of siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 45 tool updatesv0.1.0
    • RemovedAPI-batchGetAccountsActivities
    • RemovedAPI-batchGetFederatedAccountsActivities
    • RemovedAPI-get_ai_intels_api_v1_ai_intel_get
    • RemovedAPI-get_tweets_by_handle_api_v1_tweets__handle__get
    • RemovedAPI-getAccountActivities
    • RemovedAPI-getActivityById
    • RemovedAPI-getAIDataByPath
    • RemovedAPI-getAllChips
    • RemovedAPI-getAllEpochs
    • RemovedAPI-getAllNodes
    • RemovedAPI-getBridgingTransactionByHash
    • RemovedAPI-getBridgingTransactions
    • RemovedAPI-getChipById
    • RemovedAPI-getChipImageById
    • RemovedAPI-getDSLTotalRequests
    • RemovedAPI-getEpochAPYSnapshots
    • RemovedAPI-getEpochById
    • RemovedAPI-getEpochsAverageAPY
    • RemovedAPI-getEpochTransactionByHash
    • RemovedAPI-getFederatedAccountActivities
    • RemovedAPI-getFederatedActivityById
    • RemovedAPI-getFederatedNetworkActivities
    • RemovedAPI-getFederatedPlatformActivities
    • RemovedAPI-getNetworkActivities
    • RemovedAPI-getNetworkConfig
    • RemovedAPI-getNodeAssets
    • RemovedAPI-getNodeAvatarByAddress
    • RemovedAPI-getNodeByAddress
    • RemovedAPI-getNodeCountSnapshots
    • RemovedAPI-getNodeEventsByAddress
    • RemovedAPI-getNodeOperationProfitByAddress
    • RemovedAPI-getNodeOperationProfitSnapshots
    • RemovedAPI-getNodeRewardsByEpoch
    • RemovedAPI-getPlatformActivities
    • RemovedAPI-getRSS3TokenTotalSupply
    • RemovedAPI-getRSSActivityByPath
    • RemovedAPI-getStakerCountSnapshots
    • RemovedAPI-getStakerProfit
    • RemovedAPI-getStakerProfitSnapshots
    • RemovedAPI-getStakersAndNodes
    • RemovedAPI-getStakerStats
    • RemovedAPI-getStakingTransactionByHash
    • RemovedAPI-getStakingTransactions
    • RemovedAPI-getTokenTVL
    • RemovedAPI-health_check_api_v1_health_get
  2. 46 tool updates
    • First observedAPI-batchGetAccountsActivities
    • First observedAPI-batchGetFederatedAccountsActivities
    • First observedAPI-get_ai_intels_api_v1_ai_intel_get
    • First observedAPI-get_tweets_by_handle_api_v1_tweets__handle__get
    • First observedAPI-get-input-schema
    • First observedAPI-getAccountActivities
    • First observedAPI-getActivityById
    • First observedAPI-getAIDataByPath
    • First observedAPI-getAllChips
    • First observedAPI-getAllEpochs
    • First observedAPI-getAllNodes
    • First observedAPI-getBridgingTransactionByHash
    • First observedAPI-getBridgingTransactions
    • First observedAPI-getChipById
    • First observedAPI-getChipImageById
    • First observedAPI-getDSLTotalRequests
    • First observedAPI-getEpochAPYSnapshots
    • First observedAPI-getEpochById
    • First observedAPI-getEpochsAverageAPY
    • First observedAPI-getEpochTransactionByHash
    • First observedAPI-getFederatedAccountActivities
    • First observedAPI-getFederatedActivityById
    • First observedAPI-getFederatedNetworkActivities
    • First observedAPI-getFederatedPlatformActivities
    • First observedAPI-getNetworkActivities
    • First observedAPI-getNetworkConfig
    • First observedAPI-getNodeAssets
    • First observedAPI-getNodeAvatarByAddress
    • First observedAPI-getNodeByAddress
    • First observedAPI-getNodeCountSnapshots
    • First observedAPI-getNodeEventsByAddress
    • First observedAPI-getNodeOperationProfitByAddress
    • First observedAPI-getNodeOperationProfitSnapshots
    • First observedAPI-getNodeRewardsByEpoch
    • First observedAPI-getPlatformActivities
    • First observedAPI-getRSS3TokenTotalSupply
    • First observedAPI-getRSSActivityByPath
    • First observedAPI-getStakerCountSnapshots
    • First observedAPI-getStakerProfit
    • First observedAPI-getStakerProfitSnapshots
    • First observedAPI-getStakersAndNodes
    • First observedAPI-getStakerStats
    • First observedAPI-getStakingTransactionByHash
    • First observedAPI-getStakingTransactions
    • First observedAPI-getTokenTVL
    • First observedAPI-health_check_api_v1_health_get
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity between tools.

Naming Consistency5/5

With a single tool, naming inconsistency is not applicable; the pattern is internally consistent.

Tool Count2/5

A single tool for a server that likely should have many operations (RSS3 protocol) seems severely under-scoped.

Completeness1/5

The server provides only a meta-tool to get input schemas, with no actual domain operations, making it severely incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Osmosis

    jonator
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server implementation that enables LLMs to interact with the Osmosis protocol, allowing for querying and transaction functionality through natural language.
    8
    MIT

  • Agent中国通

    FRANhss
    A
    license
    A
    quality
    C
    maintenance
    这是一个面向中文圈的MCP服务器，将中国互联网常用能力（如地图、快递、RSS、B站等）封装为标准MCP工具，方便AI Agent安全调用。
    13
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RSS3-Network/mcp-server-rss3'

If you have feedback or need assistance with the MCP directory API, please join our Discord server