Telegram MCP Server

No keys or environment variables are declared in the materials, so there is no explicit credential surface or direct secret-exposure risk shown here; however, since the described function involves the Telegram Bot API, any bot token introduced in practice should be handled as a sensitive secret.

The description explicitly says it interacts with the Telegram Bot API, which implies outbound transmission of message content, forwarded content, or update requests to Telegram-related services; although no specific host is listed, this is a normal network egress pattern consistent with the stated purpose.

The system checks indicate this tool has executes-code capability, meaning the corresponding service/code runs locally; this is a standard execution surface for an MCP tool, and the materials do not show requests for extra system privileges beyond its stated function.

Per the description, the tool can send messages, forward messages, get bot information, and receive updates, so it can access message content and related Telegram metadata; the materials do not indicate local file access or broad system-data access, but it should be treated as a tool that handles chat data.

Positive factors are that the source is public and MIT-licensed, making it auditable; however, it comes from a third-party registry, has 0 stars, and an unknown maintenance status, so evidence of trustworthiness and maturity is limited and the repository and dependencies should be reviewed independently.