Repository navigation
Releases
Releases · antonio-castellon/mcp-telegram-bridge
v0.2.1
mcp-telegram-bridge 0.2.1
Non-breaking. Telegram operations are now available as a plain Python library layer, TelegramBridge, without importing the MCP server.
TelegramBridgeandSettingsare exported frommcp_telegram_bridge. Importing them does not importmcp.- The stdio server is a thin adapter over the same class. Tool names, results, and the
mcp-telegram-bridgecommand are unchanged. - All 0.2.0 security behavior (deny-by-default chat allowlist, token redaction, rate limits) applies to both the library and the server.
Upgrade: pip install -U mcp-telegram-bridge or uvx mcp-telegram-bridge@0.2.1. No configuration changes are needed coming from 0.2.0.
Commit: 693f41d
SHA256:
- mcp_telegram_bridge-0.2.1-py3-none-any.whl 9ab3fae53d7b760500a9154987bab0f848b2c68a034d6ebc3ddefc010a878c0b
- mcp_telegram_bridge-0.2.1.tar.gz 7db07946169e73ff5aa8d390b9ffa17a7eab368fa64d82eca3e7139803e86034
v0.2.0
mcp-telegram-bridge v0.2.0
Security hardening release for the stdio MCP bridge to the Telegram Bot API.
BREAKING CHANGE: chat admission
An empty ALLOWED_CHAT_IDS now denies every chat. Before, an empty list allowed all chats.
- To keep restricted use (recommended): set
ALLOWED_CHAT_IDSto your chat ids. - To allow any chat on purpose: set
ALLOW_ALL_CHATS=1(startup prints a warning to stderr). - A non-empty allowlist always wins over open mode.
Security
- Bot tokens are redacted from log records (httpx/httpcore URLs and tracebacks included); transport errors no longer carry the request URL.
- Inbound polls are bounded (limit 1..100, timeout 0..50, max text length, max update size, per-chat and global rates, poll rate). Outbound sends, edits, callback answers and getChat are rate limited.
- Messages from bots and from this bot are ignored; already returned update ids are not returned again (size-capped caches).
telegram_get_updateslabels inbound text as untrusted.SAFETY_STRICTdefaults to on and flags some instruction-override phrases (heuristic, advisory).
Supply chain
uv.lockpins dependencies with hashes; CI installs withuv sync --frozen.- GitHub Actions pinned to commit SHAs, permissions
contents: read. - Dependabot for lockfile and Actions; CI runs pip-audit and gitleaks.
Documentation
- README quick start, configuration table, threat model and residual risks;
SAFETY.mdhardening guide;SECURITY.md(security@castellon.ch). - Package contact: info@castellon.ch. Support: support@castellon.ch.
Install
pip install mcp-telegram-bridge==0.2.0
Artifacts (sha256)
- mcp_telegram_bridge-0.2.0-py3-none-any.whl 8ac53a4ca783e5a04dd31c5395a709f46bdb913792e6f2559a3f2b32784b0ca6
- mcp_telegram_bridge-0.2.0.tar.gz e717f9bded0f7669aed8e6c73535a8285948f86c1212dd83171a41c25714038e
v0.1.3
mcp-telegram-bridge 0.1.3
- Security: requires mcp>=1.30.0,<2 (fixes CVE-2026-59951 / GHSA-84m7-p3x7-pcfv). The bridge uses neither websocket_server nor Streamable HTTP.
- New CI: tests on Python 3.11, 3.12 and 3.13.
Install: uvx mcp-telegram-bridge
PyPI: https://pypi.org/project/mcp-telegram-bridge/0.1.3/
MCP Registry: io.github.antonio-castellon/mcp-telegram-bridge 0.1.3
v0.1.2
Security
- Bump
mcpto>=1.28.1,<2to clear CVE-2026-59950 / GHSA-vj7q-gjh5-988w (WebSocket Host/Origin validation in the MCP Python SDK). - This package remains stdio-only and does not use
websocket_server; the pin clears marketplace supply-chain scanners.
Meta
- Package version 0.1.2
v0.1.1 — mcp-marketplace security hardening
Changes
- Pin mcp>=1.27.2 and pytest>=9.0.3
- Atomic claim_message_tap; narrower button-map exceptions
- TelegramError context on HTTP failures
- Hardened data dir (0700/0600) via MCP_TELEGRAM_BRIDGE_DATA_DIR