F
licenseNot graded
qualityC
maintenanceEnables LLM agents to analyze Telegram channels for ad purchasing, providing insights like reach, CPM, and verdicts via MCP tools.
-
telemost-mcp-server
Related Servers
Alternatives to telemost-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to publish, edit, search, and manage messages in Telegram channels via a set of MCP tools.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP tools to be gated behind per-call USDC micropayments with direct on-chain verification and settlement, removing the need for third-party payment facilitators.MIT
- AlicenseNot gradedqualityDmaintenanceCrypto intelligence MCP: 104 tools for market data, ML signals, on-chain analytics, derivatives, and Bittensor subnets. Pay-per-call via x402 USDC on Base/Solana/Algorand/Stellar or $9.99/mo API key.MIT
- AlicenseNot gradedqualityCmaintenanceLive X/Twitter search and AI trend digests without an API key, charging per call in USDC via x402. Enables real-time tweet search and AI summaries inside MCP clients.441MIT
- AlicenseAqualityFmaintenanceExposes 177 crypto market intelligence endpoints to AI agents with automatic USDC micropayments from the user's wallet, enabling pay-per-call access without subscriptions.5931MIT
TDQS
A3.5/5.0
Scored across 20 tools
Disambiguation2/5
Several tools overlap in scope; telemost_stats_channel already includes engagement, reach, and subscriber metrics, making telemost_stats_engagement, telemost_stats_reach, and telemost_stats_subscribers partially redundant. Similarly, telemost_search and telemost_posts_search both search posts, and telemost_ads_posts adds another ambiguous post search. The boundaries between search tools and stats tools are not clear enough for reliable tool selection.
Naming Consistency3/5
All tools share the telemost_ prefix and use snake_case, but the pattern is inconsistent: some are noun-only (catalog, entities, sentiment), some use feature prefixes (stats_*, ads_*, sentiment_*), and some mix noun+verb (posts_search). The naming is readable and groups exist, but there is no uniform verb_noun structure.
Tool Count3/5
With 20 tools, the server is on the heavy side for a single-purpose API. While the domain spans analytics, ads, and search, several tools overlap and could be consolidated (e.g., stats tools). The count is not extreme but feels inflated by redundant endpoints.
Completeness4/5
The tool set covers the core Telegram data access needs: channel stats, posts, search, sentiment, entities, ads, and discovery. Minor gaps exist, such as no ability to list channels by category or country beyond keyword search, and some historical data is limited to 14 days. Overall, the domain is well covered with only small missing features.
Maintenance
ActivitySlowing
ResponsivenessNo issues