telegram-mcp-api

The HTTP API (`api.py`) binds to `0.0.0.0:8080` by default and lacks any explicit authentication or authorization mechanisms. This means anyone on the network with access to the host machine can potentially send requests to the API and control the Telegram account (send messages, delete chats, ban users, etc.) with full permissions. While the `docker-compose.yml` configuration may imply local usage, binding to `0.0.0.0` is a significant risk if deployed without strict network isolation (e.g., firewall rules). The MCP server, operating over stdio, has less network exposure, but its capabilities are equally broad. Sensitive Telegram API credentials are correctly handled via environment variables (`.env`). Input validation for chat/user IDs is present, which mitigates some basic injection risks. However, the lack of API-level access control is a critical vulnerability for the HTTP API component.