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
Available components
Last scanned (2 hours ago)
Scores higher than 46% of npm servers
Category Communication
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 115 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 223 tokens (~44/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 20 Oct 26 −5
- Source repository: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 18 Oct 26 0
- Stability: 0.97 → pass 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 5 Nov 2026 · Analysed npm/dynamic-telegram-bot-api-mcp@10.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| 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 →
telegram_call_method Call Telegram method ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true for destructive methods such as deleteMessage or banChatMember |
| method | string | yes | – |
| parameters | object | – | – |
No output schema declared.
No examples provided.
telegram_get_method Get Telegram method schema ~35
Return the complete current schema for one Telegram Bot API method.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | Method name, for example sendPhoto |
No output schema declared.
No examples provided.
telegram_get_type Get Telegram object schema ~39
Return the complete current definition of a Telegram Bot API object or union type.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Object name, for example InlineKeyboardMarkup |
No output schema declared.
No examples provided.
telegram_refresh_schema Refresh Telegram schema ~25
Fetch and atomically install the latest schema from the official Telegram Bot API documentation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
telegram_search_methods Search Telegram methods ~50
Fuzzy-search every Telegram Bot API method by name, description, category, or parameter name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| search | string | – | Search terms, for example 'send photo' |
No output schema declared.
No examples provided.
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.
npm · dynamic-telegram-bot-api-mcp
claude mcp add patricktobias86-dynamic-telegram-bot-api-mcp -- npx -y dynamic-telegram-bot-api-mcp
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 73 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 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 5 November 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.