Telegram Managed Bot Factory
PYPI · TELEGRAM-MANAGED-BOT-FACTORY · SCANNED OCT 4
Provision owner-confirmed isolated Telegram Managed Bot instances.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 47 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to laser54/telegram-managed-bot-factory). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 42 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Telegram Managed Bot Factory MCP server?
Telegram Managed Bot Factory runs locally as a PyPI package, launched with uvx telegram-managed-bot-factory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · telegram-managed-bot-factory
claude mcp add laser54-bot-factory -- uvx telegram-managed-bot-factory
{
"mcpServers": {
"laser54-bot-factory": {
"command": "uvx",
"args": [
"telegram-managed-bot-factory"
]
}
}
} {
"servers": {
"laser54-bot-factory": {
"command": "uvx",
"args": [
"telegram-managed-bot-factory"
]
}
}
} codex mcp add laser54-bot-factory -- uvx telegram-managed-bot-factory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"laser54-bot-factory": {
"type": "local",
"command": [
"uvx",
"telegram-managed-bot-factory"
],
"enabled": true
}
}
} openclaw mcp add laser54-bot-factory --command uvx --arg telegram-managed-bot-factory
mcp_servers:
laser54-bot-factory:
command: "uvx"
args: ["telegram-managed-bot-factory"] {
"McpServers": {
"laser54-bot-factory": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"telegram-managed-bot-factory"
]
}
}
} assistant mcp add laser54-bot-factory -t stdio -c uvx -a telegram-managed-bot-factory
{
"mcpServers": {
"laser54-bot-factory": {
"command": "uvx",
"args": [
"telegram-managed-bot-factory"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +3
- License: fail → pass ▲ functional
- Licence: MIT License → MIT functional
- 25 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Aug 26 0
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Analysed pypi/telegram-managed-bot-factory@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | laser54/telegram-managed-bot-factory |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/laser54/telegram-managed-bot-factory/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 2390462558 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:bcc0044cd90776716d901d197cd12e97092ebacc2aba179753e2f96f6aaa122d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 49 packages
| Packages resolved | 49 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the Telegram Managed Bot Factory MCP server?
Telegram Managed Bot Factory is an MCP server listed in the public MCP registry as io.github.laser54/bot-factory. Provision owner-confirmed isolated Telegram Managed Bot instances. This page covers its PyPI package (telegram-managed-bot-factory).
Is the Telegram Managed Bot Factory MCP server safe to use?
Telegram Managed Bot Factory scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the Telegram Managed Bot Factory MCP server still maintained?
Telegram Managed Bot Factory is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Telegram Managed Bot Factory MCP server under?
Telegram Managed Bot Factory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.