Telegram Archive
OCI · DRUMSERGIO/TELEGRAM-ARCHIVE-MCP · 2 COMPONENTS
Search and read your archived Telegram chats and messages
Available components
Last scanned (1 hour ago)
Scores higher than 62% of OCI servers
Category Search and Retrieval
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2155 tokens (~134/item across 16 items; 12 tools + 4 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Package version: v0.4.0 → v0.4.1 functional
- 27 Oct 26 0
- Package version: v0.3.1 → v0.4.0 functional
- 21 Oct 26 0
- Package version: v0.3.0 → v0.3.1 functional
- 16 Oct 26 0
- Package version: v0.2.0 → v0.3.0 functional
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 oci/drumsergio/telegram-archive-mcp@v0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_chat_stats Chat statistics ~89
Get the archive's statistics for one chat: how many messages and media files it holds, their total size, and the dates of its first and last message. Use telegram-archive://stats for the totals of the whole archive.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
Structured output declared, but exposes no named fields.
No examples provided.
get_media Look at a message's photo ~193
Get the photo or file attached to one message. A JPEG, PNG, WebP or GIF image comes back as an image you can look at, scaled to at most 1568 pixels on its longest side, after a JSON text block with the message's message_id, date, sender, text (the caption) and reply_to_msg_id, and the file's media_key, kind, file_name, mime_type, size_bytes, image_returned, width, height and scaled. Any other file returns only that JSON text block, with a note saying why the file is not included.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| message_id | integer | yes | Id of the message that carries the media; for a reply such as "see my picture", its reply_to_msg_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Naive UTC. |
| file_name | string|null | – | – |
| height | integer | – | – |
| image_returned | boolean | yes | True when an image content block follows. |
| kind | string | yes | photo, document, video, geo... |
| media_key | string | yes | – |
| message_id | integer | yes | – |
| mime_type | string|null | – | – |
| note | string | – | Why the file is not included, when it is not. |
| reply_to_msg_id | integer|null | – | – |
| scaled | boolean | – | – |
| sender | string|null | – | – |
| size_bytes | integer|null | – | – |
| text | string|null | – | The caption. |
| width | integer | – | – |
No examples provided.
get_message_context Read around a message ~164
Read the conversation around one message: the message itself with up to `before` older and `after` newer messages of the same chat, oldest first. Use it after search_messages or search_all_chats finds a hit, or to see what a reply_to_msg_id points at.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Newer messages to include, 0 to 50 (default 5). |
| before | integer | – | Older messages to include, 0 to 50 (default 5). |
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| message_id | integer | yes | Id of the message to centre on (a message's id field). |
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | yes | How many newer messages came back (fewer than asked at the end of the chat). |
| before | integer | yes | How many older messages came back (fewer than asked at the start of the chat). |
| message_id | integer | yes | The message asked for; it is in messages. |
| messages | array | yes | Oldest first: the older messages, the message itself, then the newer ones, with the same fields as get_messages. |
No examples provided.
get_messages Read a chat's messages ~323
Get messages from a Telegram chat, newest first. Page with offset, or with the keyset cursor: pass the date and id of the last message you received as before_date and before_id to get the older ones (constant time on huge chats). after_id returns the messages right after an id. Dates are naive UTC. Each message carries reply_to_msg_id and, when it has a file, media (pass its id to get_media).
| Name | Type | Req | Description |
|---|---|---|---|
| after_id | integer | – | Returns the messages right after this message id (newer), still newest first. |
| before_date | string | – | Keyset cursor: ISO 8601 date-time, naive values are UTC (e.g. 2026-06-10T18:04:17). Returns messages older than this instant; pair with before_id. |
| before_id | integer | – | Keyset cursor: message id. Returns messages with a smaller id; pair with before_date. |
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| limit | integer | – | Maximum messages to return, 1 to 500 (default 50). |
| offset | integer | – | Messages to skip, 0 to 100000 (default 0). Slow deep into a long chat; ignored when a cursor is given. |
| topic_id | integer | – | Forum topic id from get_topics; keeps only that topic's messages. 1 is the General topic. Omit for the whole chat. |
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | – | Archived messages as the viewer returns them: id, date (naive UTC), text, sender fields, reply_to_msg_id, media and more. |
No examples provided.
get_messages_by_date Read one day of a chat ~248
Get every message of a Telegram chat sent on one calendar day, oldest first. The day is taken in the given timezone (default UTC); the archive stores dates in UTC. Walks the chat with the keyset cursor, so it is cheap even on chats with hundreds of thousands of messages. Use it to answer "what was said on <day>"; use get_messages to page through a chat instead.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| date | string | yes | The calendar day, YYYY-MM-DD (e.g. 2026-06-10). |
| limit | integer | – | Maximum messages to return, 1 to 5000 (default 1000). When the day has more, the newest are dropped and truncated is true. |
| timezone | string | – | IANA timezone the date is expressed in (e.g. Europe/Madrid). Default UTC. |
| topic_id | integer | – | Forum topic id from get_topics; keeps only that topic's messages. 1 is the General topic. Omit for the whole chat. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Messages returned. |
| date | string | yes | The day asked for, YYYY-MM-DD. |
| messages | array | yes | The day's messages, oldest first, with the same fields as get_messages. |
| timezone | string | yes | IANA timezone the day was taken in. |
| topic_id | integer | – | The forum topic filter, when one was given. |
| truncated | boolean | yes | True when the day held more than limit messages and the newest were dropped. |
No examples provided.
get_pinned_messages Read pinned messages ~78
Get every pinned message of a Telegram chat, newest first, with the same fields as get_messages. Pinned messages often hold a group's rules, addresses or key links.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | – | Archived messages as the viewer returns them: id, date (naive UTC), text, sender fields, reply_to_msg_id, media and more. |
No examples provided.
get_topics List forum topics ~95
List the forum topics (threads) of a forum supergroup, with message counts. Pass a topic's id as topic_id to get_messages, search_messages or get_messages_by_date to read only that thread. A chat that is not a forum has no topics.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | – | One row per forum topic: id (the topic_id other tools take), title, message_count, last_message_date, is_closed, is_pinned. |
No examples provided.
list_chats List archived chats ~226
List archived Telegram chats, most recent first. Use this first: each chat's ref is the chat_id the other tools take. Each row also carries id (the numeric Telegram chat id), type, accounts (the archive account ids holding the chat), and its title or name. Narrow it with search (by name), archived or folder_id (from list_folders). The answer is {chats, total, limit, offset, has_more}; page with offset while has_more is true.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true keeps only chats archived in Telegram, false only the others. Omit for both. |
| folder_id | integer | – | Keep only the chats of one Telegram folder; the id comes from list_folders. |
| limit | integer | – | Maximum chats to return, 1 to 500 (default 100). |
| offset | integer | – | Number of chats to skip (default 0). |
| search | string | – | Keep chats whose title, first or last name, or username contains this text, case-insensitive (e.g. "climbing"). |
| Name | Type | Req | Description |
|---|---|---|---|
| chats | array | – | One row per chat: ref (the chat_id other tools take), id (numeric Telegram chat id), type, accounts, and its title or name. |
| has_more | boolean | – | True when another page follows; call again with offset + limit. |
| limit | integer | – | – |
| offset | integer | – | – |
| total | integer | – | Chats matching the filters, across all pages. |
No examples provided.
list_folders List chat folders ~49
List the Telegram chat folders (Telegram's dialog filters, such as Work or Family) with their ids. Pass a folder's id to list_chats as folder_id to see the chats inside it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| folders | array | – | One row per Telegram folder (dialog filter), including its id (the folder_id list_chats takes) and title. |
No examples provided.
refresh_stats Recalculate archive statistics ~87
Make the viewer recalculate the archive-wide statistics now and return them (chat, message and media counts, total size). It scans the whole archive, so it can take a while and load the viewer's database; it changes no message. Needs the viewer's master login. The cached totals in telegram-archive://stats are usually enough. Hidden when the server runs with READ_ONLY=1.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_all_chats Search every chat ~147
Search message text across every chat this archive login may see, newest first. Matching is by word prefix on the viewer's full-text index. Each hit names its chat, and chat.ref is the chat_id for get_message_context or get_messages. Use search_messages instead to search one known chat. Needs a Telegram Archive viewer with cross-chat search; an older viewer answers 404.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum hits to return, 1 to 100 (default 20). |
| offset | integer | – | Hits to skip, 0 to 5000 (default 0). |
| query | string | yes | Words to find (e.g. "climbing gym address"). |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | – | True when more hits follow; call again with offset + limit. |
| indexed | boolean | – | False while the viewer is still building its search index, so hits may be missing. |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| results | array | – | Hits, newest first: id, date (naive UTC), text, sender_name, topic_title, matched_in, and chat {ref, title, type, ...}. chat.ref is the chat_id other tools take. |
No examples provided.
search_messages Search one chat ~173
Search the messages of one chat for a keyword, newest first, and return the matching messages with the same fields as get_messages. Use search_all_chats when you do not know the chat. To read the conversation around a hit, pass its id to get_message_context.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The chat's ref, as list_chats or search_all_chats returns it (an opaque string; not the numeric Telegram id). |
| limit | integer | – | Maximum messages to return, 1 to 200 (default 20). |
| query | string | yes | Text to find in the message text (e.g. "invoice"). |
| topic_id | integer | – | Forum topic id from get_topics; keeps only that topic's messages. 1 is the General topic. Omit for the whole chat. |
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | – | Archived messages as the viewer returns them: id, date (naive UTC), text, sender fields, reply_to_msg_id, media and more. |
No examples provided.
How do I install the Telegram Archive MCP server?
Telegram Archive runs locally as a container image, launched with docker run --rm -i -e TELEGRAM_ARCHIVE_URL -e TELEGRAM_ARCHIVE_USER -e TELEGRAM_ARCHIVE_PASS -e READ_ONLY drumsergio/telegram-archive-mcp:v0.4.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · drumsergio/telegram-archive-mcp
claude mcp add geiserx-telegram-archive-mcp -- docker run --rm -i -e TELEGRAM_ARCHIVE_URL -e TELEGRAM_ARCHIVE_USER -e TELEGRAM_ARCHIVE_PASS -e READ_ONLY drumsergio/telegram-archive-mcp:v0.4.1
This image reads TELEGRAM_ARCHIVE_URL, TELEGRAM_ARCHIVE_USER, TELEGRAM_ARCHIVE_PASS and READ_ONLY. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Telegram Archive MCP server?
Telegram Archive is an MCP server listed in the public MCP registry as io.github.GeiserX/telegram-archive-mcp. Search and read your archived Telegram chats and messages. This page covers its container image (drumsergio/telegram-archive-mcp).
Is the Telegram Archive MCP server safe to use?
Telegram Archive scores 44 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.
What tools does the Telegram Archive MCP server expose?
Telegram Archive exposes 12 tools: get_chat_stats, get_media, get_message_context, get_messages, get_messages_by_date, and 7 more. Their descriptions and schemas cost roughly 1,872 tokens of context every time the server is loaded.
Is the Telegram Archive MCP server still maintained?
Telegram Archive 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.