Bragproof

← Reports

secure-telegram-mcp

Needs setup before it starts0.3.3npm

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_HASH, TELEGRAM_MCP_SESSION_PASSPHRASE_FILE, TELEGRAM_MCP_CONFIG +4
Contacts while installing and starting: nothing

0hosts contacted
0files written
220dependencies

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 secure-telegram-mcp@0.3.3

Installing a package runs its code. Use a sandbox for anything you have not read.

Its error output names these settings: TELEGRAM_API_HASH, TELEGRAM_MCP_SESSION_PASSPHRASE_FILE, TELEGRAM_MCP_CONFIG, TELEGRAM_MCP_SESSION_DIR, TELEGRAM_MCP_MEDIA_DIR, TELEGRAM_MCP_ENDPOINT, TELEGRAM_MCP_ENDPOINT_TOKEN.

What it said when it did not start
 OPTIONAL. 'setup' PROMPTS for these interactively
  TELEGRAM_API_HASH          (api_hash echo-off) — no need to export them and
                             leak them into shell history; when set they are used
                             as a pre-fill default. For Telegram MCP they are OPTIONAL
                             overrides of the credentials sealed into the session
                             at setup (the sealed values are SSOT).

Session unlock (OPTIONAL; first present wins). When none is set the
machine-bound key is used (SMOOTH posture); supplying a PIN selects the
HARDENED posture:
  TELEGRAM_MCP_SESSION_PASSPHRASE_FILE  Path to a 0600 file holding the PIN
  TELEGRAM_MCP_SESSION_PASSPHRASE       The PIN inline (*_FILE is preferred)
  TELEGRAM_MCP_SESSION_KEYFILE          Recovery keyfile for data present when it was exported

Optional environment:
  TELEGRAM_MCP_CONFIG        Config draft path (default: ~/.secure-telegram-mcp/config.json)
  TELEGRAM_MCP_SESSION_DIR   Encrypted session directory (default: ~/.secure-telegram-mcp/sessions)
  TELEGRAM_MCP_AUDIT_LOG     Audit log path (default: <session-dir>/audit.log)
  TELEGRAM_MCP_MEDIA_DIR     Shared media root (default: ~/.secure-telegram-mcp/media)
  TELEGRAM_MCP_IDLE_HOURS    PIN-protected idle auto-lock window (default: 12; 0 disables)
  TELEGRAM_MCP_ENDPOINT      Optional endpoint-name assertion (the token selects it)
  TELEGRAM_MCP_DEBUG_LOG     Owner-only setup diagnostic log (error messages are omitted)
  TELEGRAM_MCP_ENDPOINT_TOKEN  The endpoint's API key (without it, connect only lists the tools)

Written by the package or by npm, not by this site.

Install facts

LicenseMIT
Needsnode >=20.10.0
Sourcegithub.com/antonorlov/secure-telegram-mcp
Install scriptsbufferutil, es5-ext, utf-8-validate declare them. This runner does not run them.
Tarballsha512-X+xwlxfkNssSjp0+b760w0WkQWKYuDdP43n8FbI/ZiqUiDvJ0zgj/tuO+KCLQ5Li/fy5QgjAt23yZcKpV5P6NA==

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.

Show it on your README

Bragproof: Needs setup before it starts

[![Bragproof](https://bragproof.smaverk.com/badge/secure-telegram-mcp.svg)](https://bragproof.smaverk.com/r/secure-telegram-mcp)

New version out? Ask for a fresh report.