@overpod/mcp-telegram
It exited or refused to answer until it is given configuration, such as a key or an argument. Run 2026-11-16.
Needs to start: TELEGRAM_API_ID, TELEGRAM_API_HASH
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p @overpod/mcp-telegram@1.45.1 mcp-telegram
Installing a package runs its code. Use a sandbox for anything you have not read.
Its error output names these settings: TELEGRAM_API_ID, TELEGRAM_API_HASH.
What it said when it did not start
[mcp-telegram] Missing TELEGRAM_API_ID and TELEGRAM_API_HASH (required to own the Telegram connection) Get your credentials at https://my.telegram.org/apps (API development tools) Set them in .env or export as environment variables
Written by the package or by npm, not by this site.
Files it wrote
/tmp/ .mcp-telegram/ daemon.lock
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | github.com/mcp-telegram/mcp-telegram |
| Install scripts | bufferutil, es5-ext, utf-8-validate declare them. This runner does not run them. |
| Tarball | sha512-5LgN8kxmbW5db9adMvNKQWYVTyK3V9lS+4ZIY5AfdrkTRUKOv5lNX8u8x9Jo0gjtFCI7xXuTvDo3iZt9HoIYRQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40overpod/mcp-telegram)
New version out? Ask for a fresh report.