GhostPaw Telegram
NPM · @GHOSTPAW/TELEGRAM
Telegram message mirror, search, sending, and moderation tools.
Available components
Last scanned (9 hours ago)
Scores higher than 29% 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 Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to GhostPawJS/telegram). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 702 tokens (~175/item across 4 items; 4 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 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.
- 24 Oct 26 47
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 24 Oct 2026 · Analysed npm/@ghostpaw/telegram@0.6.2
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GhostPawJS/telegram |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GhostPawJS/telegram/.github/workflows/publish.yml@refs/tags/v0.6.2 |
| Rekor log index | 3441436897 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ee17059ca5e8b2d3cad5cb46843747d46fca7d043d940f64e5480cfb2d37538667e79e3a76a5df348e9b227ca4f67592aab8c5b7a3997cf97c95c34d9 |
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 →
tg_connect ~89
Query bot connection status, configuration, and chat list. Use when: Use to retrieve bot statistics, stored state values, or a list of active chats. Not for: Do not use for sending messages or moderating users.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | The state key to look up. |
| limit | integer | – | Max chats to return. |
| subcommand | string | yes | The connect subcommand. |
No output schema declared.
No examples provided.
tg_manage ~199
Moderation and chat administration: ban, unban, restrict, promote, kick users, and query member info. Use when: Plans only by default. Use createTelegramToolFacade with execute: true and a client to perform actions with configurable limits. Use when you need to moderate users, manage chat permissions, or look up member status. Not for: Do not use for sending messages or reading message history.
| Name | Type | Req | Description |
|---|---|---|---|
| canSendMessages | boolean | – | Whether the user can send messages. |
| chatId | integer | – | The chat ID. |
| deleteMessages | boolean | – | Delete messages on ban. |
| isAdmin | boolean | – | Grant or revoke admin. |
| limit | integer | – | Max members to return. |
| status | string | – | Filter by member status. |
| subcommand | string | yes | The moderation subcommand. |
| untilDate | integer | – | Unix timestamp until the action applies. |
| userId | integer | – | The user ID. |
No output schema declared.
No examples provided.
tg_read ~166
Read and query the Telegram database: messages, chats, users, reactions, and more. Use when: Use when you need to inspect stored messages, find chats or users, search text, or retrieve reaction and edit history. Not for: Do not use for sending, editing, or deleting messages.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | After this timestamp (ms) |
| before | integer | – | Before this timestamp (ms) |
| chatId | integer | – | Chat ID |
| limit | integer | – | Max results |
| messageId | integer | – | Message ID |
| query | string | – | Full-text search query |
| subcommand | string | yes | Which read operation to perform |
| threadId | integer | – | Thread ID filter |
| userId | integer | – | User ID |
No output schema declared.
No examples provided.
tg_send ~189
Outbound actions: send, edit, delete, pin/unpin messages, send typing indicator, and forward messages. Use when: Plans only by default. Use createTelegramToolFacade with execute: true and a client to perform actions with configurable limits. Use when you need to send or modify messages, show a typing indicator, or forward a message to another chat. Not for: Do not use for reading or querying stored data.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | integer | – | Chat ID |
| fromChatId | integer | – | Source chat ID |
| messageId | integer | – | Message ID |
| parseMode | string | – | Parse mode (HTML, MarkdownV2) |
| replyToMessageId | integer | – | Reply-to message ID |
| subcommand | string | yes | The send subcommand. |
| text | string | – | Message text |
| toChatId | integer | – | Destination chat ID |
No output schema declared.
No examples provided.
How do I install the GhostPaw Telegram MCP server?
GhostPaw Telegram runs locally as an npm package, launched with npx -y @ghostpaw/telegram. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ghostpaw/telegram
claude mcp add ghostpawjs-telegram -- npx -y @ghostpaw/telegram
What is the GhostPaw Telegram MCP server?
GhostPaw Telegram is an MCP server listed in the public MCP registry as io.github.GhostPawJS/telegram. Telegram message mirror, search, sending, and moderation tools. This page covers its npm package (@ghostpaw/telegram).
Is the GhostPaw Telegram MCP server safe to use?
GhostPaw Telegram scores 47 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 GhostPaw Telegram MCP server expose?
GhostPaw Telegram exposes 4 tools: tg_read, tg_send, tg_manage, tg_connect. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Is the GhostPaw Telegram MCP server still maintained?
GhostPaw Telegram is still listed as active in the MCP registry. We last reached this channel on 24 October 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 GhostPaw Telegram MCP server under?
GhostPaw Telegram declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.