not analyzable — source repository is gone (deleted or private)
MCP/HTTP Telegram Gateway — Multi-tenant, MTProto User API, 8 tools, multi-user Bearer auth, global search, session ACL, Docker
Source not yet analyzed — this grade rests on attested signals (CVEs, supply-chain) only. It is a floor: reading the code could raise it, not lower it.
- vulnerabilities attested + 50
- capability exposure inferred + 32
- abandonment inferred + 10
- trust mitigators mixed − 3
attested inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
graded 19s ago · see ecosystem CVEs →
- D · 74 → E · 89
- C · 59 → D · 74
- D · 74 → C · 59
No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.
- abandonment +10 abandonment hub →
[](https://mcpobservatory.com/servers/github:leshchenko1979/fast-mcp-telegram/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of leshchenko1979.