# io.github.patricktobias86/dynamic-telegram-bot-api-mcp (npm · dynamic-telegram-bot-api-mcp)

A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `dynamic-telegram-bot-api-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp.md), [page](https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp)

## Channel facts

- Registry: `npm`
- Package: `dynamic-telegram-bot-api-mcp`
- Version: `10.3.3`
- 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-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 33 of 118 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 223 tokens (~44/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.patricktobias86/dynamic-telegram-bot-api-mcp server?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp runs locally as an npm package, launched with npx -y dynamic-telegram-bot-api-mcp. 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 patricktobias86-dynamic-telegram-bot-api-mcp -- npx -y dynamic-telegram-bot-api-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "patricktobias86-dynamic-telegram-bot-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dynamic-telegram-bot-api-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "patricktobias86-dynamic-telegram-bot-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dynamic-telegram-bot-api-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add patricktobias86-dynamic-telegram-bot-api-mcp -- npx -y dynamic-telegram-bot-api-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "patricktobias86-dynamic-telegram-bot-api-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dynamic-telegram-bot-api-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add patricktobias86-dynamic-telegram-bot-api-mcp --command npx --arg -y --arg dynamic-telegram-bot-api-mcp
```

### Hermes

```yaml
mcp_servers:
  patricktobias86-dynamic-telegram-bot-api-mcp:
    command: "npx"
    args: ["-y", "dynamic-telegram-bot-api-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "patricktobias86-dynamic-telegram-bot-api-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dynamic-telegram-bot-api-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add patricktobias86-dynamic-telegram-bot-api-mcp -t stdio -c npx -a -y dynamic-telegram-bot-api-mcp
```

### Other

```json
{
  "mcpServers": {
    "patricktobias86-dynamic-telegram-bot-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dynamic-telegram-bot-api-mcp"
      ]
    }
  }
}
```

## 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-09-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 73, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-11 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-10 (score 55)

First indexed and scored.

## MCP tools (5)

### `telegram_search_methods` (~50 tokens)

Search Telegram methods

Fuzzy-search every Telegram Bot API method by name, description, category, or parameter name.

Input parameters:

- `limit` (integer)
- `search` (string): Search terms, for example 'send photo'

### `telegram_get_method` (~35 tokens)

Get Telegram method schema

Return the complete current schema for one Telegram Bot API method.

Input parameters:

- `method` (string, required): Method name, for example sendPhoto

### `telegram_get_type` (~39 tokens)

Get Telegram object schema

Return the complete current definition of a Telegram Bot API object or union type.

Input parameters:

- `type` (string, required): Object name, for example InlineKeyboardMarkup

### `telegram_call_method` (~74 tokens)

Call Telegram method

Validate and execute any current Telegram Bot API method. Destructive methods require confirm=true. Local files and base64 upload descriptors are converted to multipart uploads.

Input parameters:

- `confirm` (boolean): Must be true for destructive methods such as deleteMessage or banChatMember
- `method` (string, required)
- `parameters` (object)

### `telegram_refresh_schema` (~25 tokens)

Refresh Telegram schema

Fetch and atomically install the latest schema from the official Telegram Bot API documentation.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 55

## Common questions

### What is the io.github.patricktobias86/dynamic-telegram-bot-api-mcp server?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp is listed in the public MCP registry as io.github.patricktobias86/dynamic-telegram-bot-api-mcp. A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API. This page covers its npm package (dynamic-telegram-bot-api-mcp).

### Is the io.github.patricktobias86/dynamic-telegram-bot-api-mcp server safe to use?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.

### What tools does the io.github.patricktobias86/dynamic-telegram-bot-api-mcp server expose?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp exposes 5 tools: telegram_search_methods, telegram_get_method, telegram_get_type, telegram_call_method, telegram_refresh_schema. Their descriptions and schemas cost roughly 223 tokens of context every time the server is loaded.

### Is the io.github.patricktobias86/dynamic-telegram-bot-api-mcp server still maintained?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.patricktobias86/dynamic-telegram-bot-api-mcp server under?

io.github.patricktobias86/dynamic-telegram-bot-api-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/dynamic-telegram-bot-api-mcp
- Socket report: https://socket.dev/npm/package/dynamic-telegram-bot-api-mcp
- Repository: https://github.com/PrimeUpYourLife/dynamic-telegram-bot-api-mcp
- Changelog RSS feed: https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/patricktobias86-dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp