Web3 Content MCP Server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_contentC | Save web3 content (article, post, document) to the database |
| search_contentB | Search stored web3 content by keywords, tags, or blockchain |
| get_contentC | Get a specific content item by ID |
| delete_contentB | Delete a content item by ID |
| get_token_priceC | Get current price and market data for a cryptocurrency |
| get_trending_tokensA | Get trending cryptocurrencies from CoinGecko |
| add_to_watchlistC | Add a token to the watchlist for tracking |
| get_watchlistA | Get all tokens in the watchlist with current prices |
| analyze_contentB | Analyze web3 content for key insights, sentiment, and topics |
| get_web3_newsC | Fetch latest web3 news from public sources |
| list_rss_sourcesB | List all configured RSS sources for web3 news |
| add_rss_sourceB | Add a new RSS feed source |
| remove_rss_sourceB | Remove an RSS source by ID |
| fetch_rss_articlesB | Fetch new articles from RSS sources and save to database |
| get_articlesC | Get saved articles from the database |
| get_articleC | Get full article details by ID |
| mark_articleC | Mark an article as read or bookmarked |
| article_createA | 새 Web3 아티클 생성. language로 한/영 톤 전환 가능 (ko=뉴닉 스타일, en=Milk Road 스타일) |
| article_getA | 아티클을 ID로 조회합니다 |
| article_listC | 아티클 목록을 조회합니다 |
| article_updateC | 아티클을 수정합니다 |
| article_searchB | 아티클을 검색합니다 (제목+본문) |
| article_statsC | 아티클 통계를 조회합니다 |
| article_templatesB | 사용 가능한 아티클 템플릿과 톤앤매너 가이드를 조회합니다 |
| article_exportB | 아티클을 마크다운으로 내보냅니다 |
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 25 tools
Multiple tools have unclear boundaries: get_article vs article_get, get_articles vs article_list, and search_content vs article_search appear to serve the same purpose. While some tools (token prices, watchlist) are distinct, the overlapping pairs create significant misselection risk.
Naming is inconsistent, mixing verb-first (get_article) and noun-first (article_create) patterns, along with preposition-based verbs (add_to_watchlist). No uniform convention exists across the set, making it hard to predict tool names.
At 25 tools, the count is at the upper end of 'heavy' and many tools duplicate functionality (e.g., get_articles vs article_list). The set could be streamlined to ~15-18 tools without losing capability, making the current count feel slightly inflated.
The server covers article CRUD reasonably well (article_create/get/list/update/search/export) and includes content storage, RSS management, and token prices. However, there is no update operation for stored content items and no remove_from_watchlist, leaving minor lifecycle gaps.