mcp-telegram
mcp0.1.1MCP server to work with Telegram through MTProto
By sparfenyuk | 53 findings | Scanned 6/15/2026 | tooltrust-scanner/v0.3.17 | 175
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (53)
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
tg_set_my_commandstg_send_phototg_send_documenttg_send_videotg_send_audiotg_get_chat_membertg_set_webhooktg_delete_webhooktg_get_webhook_infotg_answer_callback_querytg_get_fileFix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
tg_get_metg_set_my_commandstg_send_messagetg_send_phototg_send_documenttg_send_videotg_send_audiotg_send_locationtg_send_polltg_send_contacttg_edit_message_texttg_edit_message_captiontg_delete_messagetg_get_chattg_get_chat_member_counttg_get_chat_membertg_ban_chat_membertg_unban_chat_membertg_set_webhooktg_delete_webhooktg_get_webhook_infotg_answer_callback_querytg_get_filetg_get_user_profile_photostg_pin_chat_messagetg_unpin_chat_messagetg_create_chat_invite_linkFix: Review and remediate the identified issue.
declared capabilities: code/command execution
tg_set_my_commandsdeclared capabilities: network access, filesystem access
tg_send_phototg_send_documenttg_send_videotg_send_audiotg_get_filedeclared capabilities: filesystem access
tg_delete_messagetg_get_user_profile_photostg_create_chat_invite_linkdeclared capabilities: HTTP requests
tg_get_chat_memberdeclared capabilities: network access, HTTP requests
tg_set_webhooktg_get_webhook_infodeclared capabilities: filesystem access, HTTP requests
tg_delete_webhookdeclared capabilities: network access, database access
tg_answer_callback_queryFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
tg_set_webhook:input parameter "secret_token" accepts a credential (informational; not evidence of insecure handling)
Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y mcp-telegram"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)