Skip to main content
Glama
jincai

RootData MCP Server

by jincai
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

RootData MCP Server

Introduction

这是一个基于 Model Context Protocol (MCP) 的服务器，用于集成 RootData API，提供加密货币和区块链项目的数据查询功能。

它允许 Claude 和其他 AI 助手通过 MCP 接口直接获取项目信息、机构详情和搜索结果。

Related MCP server: Flow MCP Server

Available Tools

本服务器提供以下 MCP 工具：

  • search: 根据关键词搜索项目/VC/人物的简要信息

  • get_project: 根据项目 ID 获取项目的详细信息

  • get_organization: 根据机构 ID 获取风投机构的详细信息

Setup

Prerequisites

  • Python 3.10 或更高版本

  • uv 包管理器（推荐）

Installation

  1. 克隆此仓库：

git clone https://github.com/jincai/rootdata-mcp-server
cd rootdata-mcp-server

  1. 如果你还没有安装 uv，可以安装它：

# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows
curl -LsSf https://astral.sh/uv/install.ps1 | powershell

  1. 安装依赖：

# 创建虚拟环境并激活
uv venv
source .venv/bin/activate  # Windows 上: .venv\Scripts\activate

# 安装依赖
uv add "mcp[cli]" httpx python-dotenv

  1. 设置环境变量：

# 创建 .env 文件存储 API 密钥
cp .env.example .env

# 在 .env 文件中设置 API 密钥
ROOTDATA_API_KEY=your-rootdata-api-key

  1. 运行服务器：

uv run server.py

Connecting to Claude Desktop

  1. 安装 Claude Desktop（如果你还没有安装）

  2. 创建或编辑 Claude Desktop 配置文件：

# macOS
mkdir -p ~/Library/Application\ Support/Claude/
nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

  1. 添加以下配置：

{
  "mcpServers": {
    "rootdata": {
      "command": "/path/to/uv",
      "args": [
        "--directory",
        "/absolute/path/to/rootdata-mcp-server",
        "run",
        "server.py"
      ]
    }
  }
}

将 /path/to/uv 替换为 which uv 的结果，将 /absolute/path/to/rootdata-mcp-server 替换为此项目的绝对路径。

  1. 重启 Claude Desktop

  2. 现在你应该能在 Claude Desktop 的工具菜单（锤子图标）中看到 RootData 工具

  3. 尝试向 Claude 提问，例如：

    • "搜索以太坊相关的项目"

    • "获取项目 ID 为 12 的详细信息"

    • "查询机构 ID 为 219 的风投机构信息"

License

MIT

Available Tools

3 tools
get_organizationC

Obtain VC details according to VC ID.

Args:
    org_id: Organization ID
    include_team: Whether to include team member information, default is false.
    include_investments: Whether it includes investment project information, default is false.
ParametersJSON Schema
NameRequiredDescriptionDefault
org_idYes
include_teamNo
include_investmentsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read-only operation ('Obtain'), but doesn't specify if it's safe, requires authentication, has rate limits, or what happens on errors. The description adds minimal context beyond the basic retrieval action, failing to compensate for the lack of annotations.

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

Conciseness4/5

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

The description is front-loaded with the purpose, followed by a structured 'Args' section that efficiently lists parameters with brief explanations. It avoids unnecessary fluff, though the phrasing 'Obtain VC details according to VC ID' is slightly redundant and could be more polished.

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

Completeness3/5

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

Given the tool's moderate complexity (3 parameters, 1 required), no annotations, but an output schema exists, the description is minimally adequate. It covers the purpose and parameters but lacks behavioral context and usage guidelines. The output schema reduces the need to explain return values, but overall completeness is limited by gaps in transparency and guidance.

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

Parameters4/5

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

The schema description coverage is 0%, so the description carries the burden of explaining parameters. It clearly defines 'org_id' as 'Organization ID' and provides meaningful semantics for 'include_team' and 'include_investments' with default values, adding significant value beyond the bare schema. However, it doesn't detail data types or constraints, keeping it from a perfect score.

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

Purpose3/5

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

The description states the tool 'Obtain VC details according to VC ID,' which clarifies it retrieves information about venture capital organizations. However, it's somewhat vague about what 'VC details' specifically include beyond the optional team and investment parameters, and it doesn't differentiate from sibling tools like 'get_project' or 'search' in terms of scope or use case.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'get_project' or 'search.' It lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent without clear direction on tool selection in relation to siblings.

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

get_projectB

Obtain project details according to the project ID.

Args:
    project_id: The unique identifier for the project.
    include_team: Whether to include team member information, default is false.
    include_investors: Whether to include investor information, default is false.
ParametersJSON Schema
NameRequiredDescriptionDefault
project_idYes
include_teamNo
include_investorsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it describes the basic operation, it doesn't mention whether this is a read-only operation, if it requires authentication, what happens with invalid project IDs, or any rate limits. The description is functional but lacks important behavioral context.

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

Conciseness4/5

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

The description is well-structured and appropriately sized. The purpose is stated clearly in the first sentence, followed by a parameter section. While efficient, the parameter explanations could be slightly more concise, and the overall description could benefit from more usage context.

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 that there's an output schema (which handles return values), the description provides good coverage of the tool's purpose and parameters. However, for a tool with no annotations and sibling tools available, it should include more guidance on when to use this versus alternatives and mention any behavioral constraints.

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

Parameters5/5

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

The description provides excellent parameter semantics that go beyond the input schema. While the schema has 0% description coverage, the description clearly explains what each parameter does ('unique identifier for the project', 'whether to include team member information', 'whether to include investor information') and provides default values. This fully compensates for the schema's lack of descriptions.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Obtain') and resource ('project details'), making it easy to understand what the tool does. However, it doesn't differentiate this tool from its sibling 'get_organization' or explain how it differs from 'search' for project-related queries.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_organization' or 'search'. It mentions default values for optional parameters but doesn't explain scenarios where including team or investor information would be beneficial.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get_organization retrieves VC details, get_project retrieves project details, and search performs keyword-based searches across multiple entity types. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific objectives.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_organization, get_project, and search. The naming is uniform, using snake_case throughout, with clear and predictable verbs that accurately describe each tool's action.

Tool Count3/5

With only 3 tools, the server feels thin for a data-focused domain like VC and project details. While the tools cover basic retrieval and search, the scope suggests that additional operations (e.g., listing, filtering, or updating) might be expected, making the count borderline for comprehensive coverage.

Completeness3/5

The server provides read operations (get and search) but lacks create, update, or delete tools, which are typical for data management. This creates notable gaps in lifecycle coverage, as agents cannot modify or add data, limiting the server to query-only functionality.

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

  • MCP Expert Server

    crazyrabbitLTC
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.
    19
    3
    MIT

  • Flow MCP Server

    lmcmz
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to access Flow blockchain data and perform operations such as checking balances, resolving domains, executing scripts, and submitting transactions.
    1
  • Blockscout MCP Server by blockscout

    Blockscout MCP Serverofficial

    blockscout
    F
    license
    A
    quality
    B
    maintenance
    A server that exposes blockchain data (balances, tokens, NFTs, contract metadata) via the Model Context Protocol, enabling AI agents and tools to access and analyze blockchain information contextually.
    18
    44

Appeared in Searches

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/jincai/rootdata-mcp-server'

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