# Telegram Managed Bot Factory (pypi · telegram-managed-bot-factory)

Provision owner-confirmed isolated Telegram Managed Bot instances.

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- pypi · `telegram-managed-bot-factory`: 37/100 (this document), [markdown](https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory.md), [page](https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory)

## Channel facts

- Registry: `pypi`
- Package: `telegram-managed-bot-factory`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 48 of 50 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - Dependency health was assessed across the 48 of 50 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (MIT License) isn't a recognized OSI-approved license.
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package 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.

## Install

### 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.

### Claude

```bash
claude mcp add laser54-bot-factory -- uvx telegram-managed-bot-factory
```

### Cursor

```json
{
  "mcpServers": {
    "laser54-bot-factory": {
      "command": "uvx",
      "args": [
        "telegram-managed-bot-factory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "laser54-bot-factory": {
      "command": "uvx",
      "args": [
        "telegram-managed-bot-factory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add laser54-bot-factory -- uvx telegram-managed-bot-factory
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "laser54-bot-factory": {
      "type": "local",
      "command": [
        "uvx",
        "telegram-managed-bot-factory"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add laser54-bot-factory --command uvx --arg telegram-managed-bot-factory
```

### Hermes

```yaml
mcp_servers:
  laser54-bot-factory:
    command: "uvx"
    args: ["telegram-managed-bot-factory"]
```

### Netclaw

```json
{
  "McpServers": {
    "laser54-bot-factory": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "telegram-managed-bot-factory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add laser54-bot-factory -t stdio -c uvx -a telegram-managed-bot-factory
```

### Other

```json
{
  "mcpServers": {
    "laser54-bot-factory": {
      "command": "uvx",
      "args": [
        "telegram-managed-bot-factory"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-22 (score 37, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-21 (score 22, −15)

- [security regression] Malware scan: pass → unverified

### 2026-08-11 (score 37, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 36)

First indexed and scored.

## MCP tools (0)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory#diagnostics

## Score history

- 2026-08-22: 37
- 2026-08-21: 22
- 2026-08-20: 37
- 2026-08-19: 37
- 2026-08-18: 37
- 2026-08-17: 37
- 2026-08-16: 37
- 2026-08-15: 37
- 2026-08-14: 37
- 2026-08-13: 37
- 2026-08-12: 37
- 2026-08-11: 37
- 2026-08-10: 36
- 2026-08-09: 36

## Common questions

### 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 37 out of 100 on VerifyMCP. 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 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/telegram-managed-bot-factory/
- Socket report: https://socket.dev/pypi/package/telegram-managed-bot-factory
- Repository: https://github.com/laser54/telegram-managed-bot-factory
- Changelog RSS feed: https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory.xml
- Changelog JSON feed: https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory.json
- HTML version of this page: https://verifymcp.io/servers/laser54-bot-factory/telegram-managed-bot-factory