Home / MCP registry index / io.telemost/telemost-mcp-server
io.telemost/telemost-mcp-server
io.telemost/telemost-mcp-server in the official MCP registry.
Endpoint https://api.telemost.io/mcp. Source: github.com/slava01011910-ops/telemost-mcp-server.
The registry describes it as: Telegram channel analytics and statistics for AI agents, pay-per-call in USDC via x402.
We read its 20 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
telemost_catalog telemost_messages telemost_search telemost_entities telemost_sentiment telemost_sentiment_llm telemost_channel_info telemost_post telemost_posts_search telemost_ads_networks telemost_ads_posts telemost_stats_channel telemost_stats_subscribers telemost_stats_mentions telemost_stats_words telemost_stats_reach telemost_dictionaries telemost_similar telemost_compilations telemost_stats_engagement
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-telemost-telemost-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.