Telegram Dev
PYPI · TELEGRAM-DEV
Current official Telegram and TON docs: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk
Available components
Last scanned (16 hours ago)
Scores higher than 75% of PyPI servers
Category Code Search and Documentation
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Kay0k1/telegram-dev). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2376 tokens (~237/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Nov 26 64
First indexed and scored.
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 21 Nov 2026 · Analysed pypi/telegram-dev@0.9.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 | Kay0k1/telegram-dev |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Kay0k1/telegram-dev/.github/workflows/release.yml@refs/tags/v0.9.0 |
| Rekor log index | 3794295569 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6326df0d1aef4a89d5bb4dbe03ffdf7027f4ffca58a771a2b9cba22567515eac |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| 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 →
check_bot_api_call Check a Bot API call ~252
Check a Bot API request against the current official schema before running or shipping code. Reports errors (unknown method or parameter with suggestions, missing required parameters, wrong types, values outside the documented list, a wrong `type` in union objects such as InputMedia) and warnings (lengths outside documented limits, parameters retired in an older Bot API version with the changelog entry that replaced them, numbers or booleans sent as strings). It does not call Telegram and cannot check permissions, chat state or file contents. Returns `valid` (true when there are no errors), `errors` and `warnings` as lists of {path, message} where path points into params (for example `reply_markup.inline_keyboard[0][0].style`), plus `url`, `bot_api_version` and freshness. An unknown method returns `valid: false` with suggestions. Use `get_bot_api_definition` to read the definitions it checks against.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | Bot API method name, e.g. 'sendMessage'. |
| params | object | yes | The request parameters exactly as your code sends them, as a JSON object. Nested objects such as reply_markup may be objects or JSON strings. |
No output schema declared.
No examples provided.
check_telegram_project Check a bot project ~305
Check every Bot API call in a Python bot project (aiogram, python-telegram-bot, pyTelegramBotAPI, raw HTTP requests) against the current official schema in one run. Use it after changing an existing bot, before an upgrade, or when asked to review a bot: it reads the whole project locally and returns only findings, so the documentation does not have to enter the context. Errors: values outside the documented list (for example `style="red"`), unknown methods or parameters in raw API requests. Warnings: parameters Telegram retired, with the Bot API version and changelog entry that replaced them; keyword arguments that are neither Bot API parameters nor known library options; bot methods with no Bot API counterpart. It does not run code, follow variables or check required parameters. Returns `findings` ({file, line, severity, call, message}), `errors`, `warnings`, `files_scanned`, declared `libraries` with versions and `bot_api_version`. To check one request instead use `check_bot_api_call`. The same check runs in a shell or CI as `telegram-dev check PATH`.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | array | – | Glob patterns relative to path to skip, e.g. ['tests/*', 'migrations/*']. |
| max_findings | integer | – | Maximum number of findings to return; totals always count everything. |
| path | string | yes | Absolute path to the bot project directory or a single Python file on this machine. |
No output schema declared.
No examples provided.
get_bot_api_definition Bot API method or type definition ~242
Return the current definition of one Bot API method or type as structured data. Use it instead of reading the whole Bot API page when you need a method's parameters or a type's fields: each entry has its type, whether it is required, the description and any allowed values or length limits stated by Telegram, plus the changelog entries that mention it. For behaviour explained in prose elsewhere (formatting, payments, limits pages) use `search_telegram_docs` and `get_telegram_document`. Returns `kind` (method or type), `name`, `url`, `description`, then `params` (methods; with `returns`) or `fields` (types; or `one_of` for union types), plus `changes`, `bot_api_version`, `source`, `checked_at` and `freshness`. An unknown name returns `kind: null` with close-match `suggestions`. Built from the cached official page, refreshed when stale.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact Bot API method or type name, e.g. 'sendMessage', 'InlineKeyboardButton', 'ReplyParameters'. Case-insensitive; close matches are suggested. |
No output schema declared.
No examples provided.
get_telegram_corpus_status Cache coverage and freshness ~198
Report how complete and how current the local documentation cache is, as totals. Use it at the start of a task or when search results look incomplete. Returns `pages`, per-area counts (`families`), crawl queue state (`frontier`), `stale_pages`, last and oldest successful checks, `refresh_policy` and up to 15 recent source `errors`. For the configured entry points use `list_telegram_sources`; for the individual cached pages use `list_telegram_cached_pages`; to answer a question use `search_telegram_docs`. Refreshing is automatic (on read, on search and in a background cycle), so there is no refresh command. Returns page counts per area, crawl queue state, stale page count, last and oldest successful checks, refresh policy and the latest source errors. Indexed pages are not all of Telegram's knowledge: absence from the cache is not evidence that a feature does not exist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_telegram_document Read an official documentation page ~293
Read the text of an official Telegram, TON or bot-library documentation page, one window at a time. Use it to read requirements, parameters and limits in full after `search_telegram_docs` found the page, or to load an entry page from `list_telegram_sources` into an empty cache. Do not use it to find which page answers a question: search first. Pages missing from the cache or older than the freshness limit (6 hours by default) are fetched first. Returns title, URL, Markdown `body` for the requested window, `next_offset` (null at the end), `total_characters`, content hash and freshness. If the live source fails, the cached text is returned with `freshness.stale` and `refresh_error` set. The observation date is when this installation read the page, not when Telegram changed it.
| Name | Type | Req | Description |
|---|---|---|---|
| length | integer | – | Number of characters to return. |
| offset | integer | – | Character offset to start from; use a search result's document_offset or the previous next_offset. |
| refresh | boolean | – | Force a live check of the source even if the cached copy is fresh. |
| url | string | yes | Official page URL from search results or list_telegram_sources, e.g. https://core.telegram.org/bots/api or https://docs.ton.org/applications/ton-connect/overview. Pages outside the official sources a… |
No output schema declared.
No examples provided.
list_bot_api_changes Bot API changes by version ~247
List official Bot API changelog entries as structured releases: version, date, link and the individual changes. Use it when upgrading a bot or a library ("what changed since 9.0?"), when a field seems new or missing, or to find when a method or field was added, replaced or removed. Returns `current_version` and `releases`, newest first: each has `version`, `date`, `url` and `changes` ({text, topic, refs: linked methods and types, terms: field and parameter names}). A name that no change mentions returns an empty list. For the full current definition use `get_bot_api_definition`; for TON or library changelogs use `search_telegram_docs` with area `ton-releases` or the library area.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of releases when since_version is empty. |
| name | string | – | Only changes that mention this method, type, field or parameter, e.g. 'InlineKeyboardButton' or 'reply_parameters'. |
| since_version | string | – | Only releases newer than this Bot API version, e.g. '9.0'. Empty returns the latest releases. |
No output schema declared.
No examples provided.
list_telegram_cached_pages List cached documentation pages ~194
List the documentation pages already stored in the local cache, sorted by URL. Use it to see which pages of an area are available offline or to pick a page to open with `get_telegram_document`. Filter with `area`, page through results with `offset` and `limit`. Returns `pages` (url, title, area, checked_at, freshness), `total` matching pages and `next_offset` to pass back for the next page (null at the end). It lists stored pages only; to find content by topic use `search_telegram_docs`, and for totals and errors use `get_telegram_corpus_status`.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Only pages from this documentation area; empty lists all areas. |
| limit | integer | – | Maximum number of pages to return. |
| offset | integer | – | Number of pages to skip, for paging through long lists; use the previous next_offset. |
No output schema declared.
No examples provided.
list_telegram_document_revisions Observed revisions of a page ~159
List the revisions of one documentation page that this installation has observed, newest first. Use it to see whether a page changed since an earlier read. To read the current text use `get_telegram_document`. Returns `revisions`: a list of {sha, captured_at, characters}, newest first. A page that this installation has never fetched returns an empty list; a URL outside the official sources is rejected with an error. It does not reconstruct history before the page was first fetched here; for Telegram release history use `list_bot_api_changes` or the changelogs (area `releases` or `ton-releases`).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Official page URL, the same form accepted by get_telegram_document. |
No output schema declared.
No examples provided.
list_telegram_sources Official documentation entry points ~149
List the official entry points this server crawls, each with its documentation area. Use it to find where to start reading for an unfamiliar area (for example the Bot API index, docs.ton.org/llms.txt or a library's docs) and pass the URL to `get_telegram_document`. If you already know the feature or API name, use `search_telegram_docs` instead. Returns `sources`: a list of {url, area} in the configured order (Telegram core docs, then TON, then bot libraries), and a short `scope` note. This is the source configuration, not the cache: `list_telegram_cached_pages` shows what is already stored.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_telegram_docs Search Telegram and TON docs ~266
Find the official documentation sections that answer a Telegram or TON development question. Use it before writing or reviewing code that calls the Bot API, Mini Apps JS, Telegram API/MTProto, TDLib, TON Connect, Tolk contracts or the aiogram, python-telegram-bot and grammY libraries. Returns up to `limit` sections with page URL, heading, excerpt, `document_offset` and freshness. Excerpts are partial: open the page with `get_telegram_document` at `document_offset` before relying on details. Stale matching pages are re-fetched first. An empty result is not proof that a feature does not exist; if the cache is empty, the response suggests pages to fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Limit results to one documentation area; empty searches all areas. Core Telegram docs rank above library docs unless the query names a library. |
| limit | integer | – | Maximum number of matching sections to return. |
| query | string | yes | Exact API names or short English keywords work best, e.g. 'InlineKeyboardButton style', 'sendVideoNote', 'ton_proof', 'jetton transfer', 'aiogram Router callback_query'. Common Russian feature words… |
No output schema declared.
No examples provided.
How do I install the Telegram Dev MCP server?
Telegram Dev runs locally as a PyPI package, launched with uvx telegram-dev serve. 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-dev
claude mcp add kay0k1-telegram-dev -- uvx telegram-dev serve
What is the Telegram Dev MCP server?
Telegram Dev is an MCP server listed in the public MCP registry as io.github.Kay0k1/telegram-dev. Current official Telegram and TON docs: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk. This page covers its PyPI package (telegram-dev).
Is the Telegram Dev MCP server safe to use?
Telegram Dev scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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.
What tools does the Telegram Dev MCP server expose?
Telegram Dev exposes 10 tools: search_telegram_docs, get_telegram_document, get_telegram_corpus_status, list_telegram_document_revisions, list_telegram_sources, and 5 more. Their descriptions and schemas cost roughly 2,305 tokens of context every time the server is loaded.
Is the Telegram Dev MCP server still maintained?
Telegram Dev is still listed as active in the MCP registry. We last reached this channel on 21 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 Telegram Dev MCP server under?
Telegram Dev declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Telegram Dev MCP server?
VerifyMCP ran 15 checks on Telegram Dev, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Telegram Dev: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.