crypto-projects-mcp
Криптопроекты MCP сервер
Сервер MCP, который предоставляет данные о криптовалютных проектах из Mobula.io агентам ИИ.
Функции
Извлечение данных проекта : получение полной информации о проекте (например, рыночных данных, токеномики и ссылок) из Mobula.
Структурированный вывод : форматирование данных проекта в хорошо организованный документ Markdown с разделами для обзора, рыночных данных, инвесторов, бирж, распределения токенов и графиков выпуска.
Поддержка языков : настройка языка вывода на основе региональных настроек системы или указанных пользователем настроек.
Related MCP server: crypto-news-mcp
Установка
Предпосылки
Python 3.10 или выше
uv для управления пакетами и запуска проекта
Доступ к API Mobula (для публичных конечных точек аутентификация не требуется)
Настраивать
Клонировать репозиторий :
git clone https://github.com/kukapay/crypto-projects-mcp.git cd crypto-projects-mcpУстановить зависимости :
uv sync
Использование
Работа в режиме разработки
Протестируйте сервер с помощью MCP Inspector:
uv run mcp dev main.pyИнтеграция с Claude Desktop
Установите сервер в Claude Desktop для взаимодействия с LLM:
uv run mcp install main.py --name "Crypto Projects"Пример взаимодействия
Сервер предоставляет два основных интерфейса: инструмент для извлечения необработанных данных и подсказку для их форматирования в структурированный документ Markdown.
1. Использование инструмента get_project_data
Инструмент get_project_data извлекает необработанные данные JSON для указанного проекта криптовалюты. Это полезно для приложений, которым нужны необработанные данные.
await get_project_data("avalanche")Это возвращает словарь, содержащий такие данные, как цена, рыночная капитализация, блокчейн и социальные ссылки для Avalanche. Пример вывода:
{
"name": "Avalanche",
"symbol": "AVAX",
"blockchains": ["Avalanche C-Chain"],
"price": 35.12,
"market_cap": 1234567890,
...
}2. Использование подсказки format_project_data
Подсказка format_project_data извлекает данные с помощью инструмента get_project_data и форматирует их в комплексный документ Markdown. Эта подсказка предназначена для приложений LLM для представления структурированной, понятной человеку информации о криптовалютном проекте.
# format_project_data("avalanche") # use system locale
format_project_data("avalanche", lang="en_US") # use en_USЭто создает документ Markdown с подробными разделами. Пример вывода для Avalanche:
# Avalanche Project Information
## Overview
- **Name**: Avalanche
- **Symbol**: AVAX
- **Chain**: Avalanche C-Chain
- **Contract Address**: 0xb31f66aa3c1e785363f0875a1b74e27b85fd66c7
- **Audit Report**: https://quantstamp.com/blog/quantstamp-enhancing-the-security-of-avalanche
- **Description**: Avalanche is a high throughput smart contract blockchain platform. Validators secure the network through a proof-of-stake consensus protocol. It is said to be fast, low cost, and environmental friendly.
## Market Data
- **Price**: $19.45
- **Market Cap**: $8,130,398,992
- **Volume (24h)**: $48,238,792
- **Total Supply**: 454,405,245
- **Circulating Supply**: 417,951,478
## Links
- **Website**: https://www.avax.network
- **Twitter**: https://twitter.com/avax
- **Discord**: https://www.avax.network/
## Investors
- **Lead Investor**: Yes
- **Name**: Polychain Capital
- **Type**: Ventures Capital
- **Description**: Polychain Capital is a cryptocurrency-focused investment management firm and hedge fund.
- **Lead Investor**: Yes
- **Name**: Dragonfly Capital
- **Type**: Ventures Capital
- **Description**: Dragonfly Capital Partners is a venture capital firm that focuses on investments in the blockchain and cryptocurrency space.
- **Lead Investor**: Yes
- **Name**: Bitmain
- **Type**: Ventures Capital
- **Description**: Bitmain is a China-based technology company that specializes in the design and manufacture of hardware for cryptocurrency mining.
- **Lead Investor**: Yes
- **Name**: Galaxy
- **Type**: Ventures Capital
- **Description**: Galaxy is a digital asset and blockchain leader helping institutions, startups, and qualified individuals shape a changing economy.
- **Lead Investor**: Yes
- **Name**: NGC Ventures (NEO Global Capital)
- **Type**: Ventures Capital
- **Description**: NGC Ventures is one of the largest institutional investors of blockchain technologies.
- **Lead Investor**: Yes
- **Name**: Initialized Capital
- **Type**: Ventures Capital
- **Description**: Not available
- **Lead Investor**: Yes
- **Name**: Three Arrows Capital
- **Type**: Ventures Capital
- **Description**: Not available
- **Lead Investor**: No
- **Name**: a16z (Andreessen Horowitz)
- **Type**: Ventures Capital
- **Description**: Andreessen Horowitz is a prominent venture capital firm based in Menlo Park, California.
- **Lead Investor**: No
- **Name**: Fundamental Labs
- **Type**: Ventures Capital
- **Description**: An investment company specialized in Blockchain sector.
- **Lead Investor**: No
- **Name**: Lemniscap
- **Type**: Ventures Capital
- **Description**: Lemniscap is an investment firm specializing in investments in emerging cryptoassets and blockchain companies.
- **Lead Investor**: No
- **Name**: Naval Ravikant
- **Type**: Angel Investor
- **Description**: Naval Ravikant is the CEO and a co-founder of AngelList.
- **Lead Investor**: No
- **Name**: MetaStable Capital
- **Type**: Ventures Capital
- **Description**: Manage Crypto Asset Hedge Funds.
- **Lead Investor**: No
- **Name**: LedgerPrime
- **Type**: Ventures Capital
- **Description**: LedgerPrime is a quantitative and systematic digital asset investment firm.
- **Lead Investor**: No
- **Name**: Digital Asset Capital Management (DACM)
- **Type**: Ventures Capital
- **Description**: Specialist, global investment manager in the digital asset sector.
- **Lead Investor**: No
- **Name**: HashKey Capital
- **Type**: Ventures Capital
- **Description**: HashKey Capital is a blockchain and cryptocurrency-focused venture capital and investment firm.
- **Lead Investor**: No
- **Name**: Balaji Srinivasan
- **Type**: Angel Investor
- **Description**: Balaji S. Srinivasan is the CTO of Coinbase and cofounder of Counsyl, Earn, Teleport, and Coin Center.
## Exchanges
- Binance: AVAX/USDT
- Coinbase: AVAX/USD
- OKX: AVAX/USDT
- Bybit: AVAX/USDT
- Kraken: AVAX/EUR
- WhiteBIT: Not available
- HTX: Not available
- P2B: Not available
- KuCoin: Not available
- Bitunix: Not available
## Token Distribution
- Foundation: 9.26%
- Airdrop: 2.5%
- Team: 10%
- Public Sale Option A1: 1%
- Public Sale Option A2: 8.3%
- Public Sale Option B: 0.67%
- Community and Development Endowment: 7%
- Testnet Incentive Program: 0.31%
- Strategic Partners: 5%
- Staking Rewards: 50%
- Private Sale: 3.46%
- Seed Sale: 2.5%
## Token Release Schedule
- Sep 2020: 40,466,016 tokens (Seed Round, Private Sale, Public Sales, etc.)
- Dec 2020: 45,188,596.8 tokens (Team, Airdrop, Foundation, etc.)
- Mar 2021: 45,188,596.8 tokens (Team, Airdrop, Foundation, etc.)
- Jun 2021: 45,188,596.8 tokens (Team, Airdrop, Foundation, etc.)
- Sep 2021: 19,502,596.8 tokens (Team, Airdrop, Foundation, etc.)
- Dec 2021: 19,502,596.8 tokens (Team, Airdrop, Foundation, etc.)
- Mar 2022: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Jun 2022: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Sep 2022: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Dec 2022: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Mar 2023: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Jun 2023: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Sep 2023: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Dec 2023: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Mar 2024: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Jun 2024: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Sep 2024: 9,541,800 tokens (Team, Airdrop, Foundation, Strategic Partners)
- Dec 2024: 1,666,800 tokens (Foundation)
- Mar 2025: 1,666,800 tokens (Foundation)
- Jun 2025: 1,666,800 tokens (Foundation)
- Sep 2025: 1,666,800 tokens (Foundation)
- Dec 2025: 1,666,800 tokens (Foundation)
- Mar 2026: 1,666,800 tokens (Foundation)
- Jun 2026: 1,666,800 tokens (Foundation)
- Sep 2026: 1,666,800 tokens (Foundation)
- Dec 2026: 1,666,800 tokens (Foundation)
- Mar 2027: 1,666,800 tokens (Foundation)
- Jun 2027: 1,666,800 tokens (Foundation)
- Sep 2027: 1,666,800 tokens (Foundation)
- Dec 2027: 1,666,800 tokens (Foundation)
- Mar 2028: 1,666,800 tokens (Foundation)
- Jun 2028: 1,666,800 tokens (Foundation)
- Sep 2028: 1,666,800 tokens (Foundation)
- Dec 2028: 1,666,800 tokens (Foundation)
- Mar 2029: 1,666,800 tokens (Foundation)
- Jun 2029: 1,666,800 tokens (Foundation)
- Sep 2029: 1,666,800 tokens (Foundation)
- Dec 2029: 1,666,800 tokens (Foundation)
- Mar 2030: 1,666,800 tokens (Foundation)Лицензия
Этот проект лицензирован по лицензии MIT. Подробности см. в файле LICENSE .
Available Tools
1 toolget_project_dataC
Fetch cryptocurrency project data from Mobula API.
Args:
token_symbol (str): The symbol of the cryptocurrency token (e.g., 'BTC', 'ETH')
Returns:
dict: Raw JSON response from Mobula API containing project details
| Name | Required | Description | Default |
|---|---|---|---|
| token_symbol | Yes |
TDQS
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. It mentions the API source and return format, but lacks details on error handling, rate limits, authentication needs, or whether it's read-only/destructive. This leaves significant gaps for a tool interacting with an external API.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized with three sentences: purpose, parameter explanation, and return value. It's front-loaded with the main action and avoids unnecessary details, though the structure could be slightly more polished.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain the response structure beyond 'raw JSON', error cases, or API limitations, which is inadequate for a tool fetching external data.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining the parameter's purpose (cryptocurrency token symbol) and providing examples ('BTC', 'ETH'), which helps beyond the bare schema. However, it doesn't cover constraints like valid symbols or format details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Fetch') and resource ('cryptocurrency project data from Mobula API'), making the purpose understandable. However, it doesn't differentiate from siblings since none exist, so it can't achieve the highest score for sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, prerequisites, or context for its application. It only states what it does without usage instructions.
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.
1 tool update
v1.0.0- First observed
get_project_data
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (get_project_data), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a server named 'crypto-projects-mcp', which suggests a broader scope. This minimal set severely limits functionality, as it only supports fetching data without any create, update, delete, or search operations.
The tool surface is severely incomplete for the implied domain of cryptocurrency projects. It lacks essential operations like listing projects, searching, updating, or deleting data, making it inadequate for typical agent workflows in this domain.
Maintenance
Related MCP Connectors
MCP server giving AI agents one-connection access to crypto & DeFi data: DeFi protocol TVL, stableco
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
- UnifAPIOAuthcom.unifapi
Hosted MCP server for live public-data APIs and Skills for AI agents.
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides real-time cryptocurrency news sourced from NewsData for AI agents.15MIT
- FlicenseAqualityDmaintenanceAn MCP server that enables AI agents to fetch real-time cryptocurrency prices and market data using the CoinGecko API.13-
- AlicenseAqualityDmaintenanceThe first blockchain & cryptocurrency MCP server that connects AI agents to Ethereum, Solana, Bitcoin, and cryptocurrency markets.98 npmMIT