io.github.auroracapital/claude-ops-telegram-server
NPM · CLAUDE-OPS-TELEGRAM-SERVER · SCANNED SEP 20
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
Available components
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 Security97
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 58 of 142 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency48
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 153 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 221 tokens (~55/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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
How do I install the io.github.auroracapital/claude-ops-telegram-server MCP server?
io.github.auroracapital/claude-ops-telegram-server runs locally as an npm package, launched with npx -y claude-ops-telegram-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · claude-ops-telegram-server
claude mcp add auroracapital-claude-ops-telegram-server -- npx -y claude-ops-telegram-server
{
"mcpServers": {
"auroracapital-claude-ops-telegram-server": {
"command": "npx",
"args": [
"-y",
"claude-ops-telegram-server"
]
}
}
} {
"servers": {
"auroracapital-claude-ops-telegram-server": {
"command": "npx",
"args": [
"-y",
"claude-ops-telegram-server"
]
}
}
} codex mcp add auroracapital-claude-ops-telegram-server -- npx -y claude-ops-telegram-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"auroracapital-claude-ops-telegram-server": {
"type": "local",
"command": [
"npx",
"-y",
"claude-ops-telegram-server"
],
"enabled": true
}
}
} openclaw mcp add auroracapital-claude-ops-telegram-server --command npx --arg -y --arg claude-ops-telegram-server
mcp_servers:
auroracapital-claude-ops-telegram-server:
command: "npx"
args: ["-y", "claude-ops-telegram-server"] {
"McpServers": {
"auroracapital-claude-ops-telegram-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"claude-ops-telegram-server"
]
}
}
} assistant mcp add auroracapital-claude-ops-telegram-server -t stdio -c npx -a -y claude-ops-telegram-server
{
"mcpServers": {
"auroracapital-claude-ops-telegram-server": {
"command": "npx",
"args": [
"-y",
"claude-ops-telegram-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 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 20 Sept 2026 · Analysed npm/claude-ops-telegram-server@0.2.1
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 →
Dependencies 142 packages
| Packages resolved | 142 |
|---|---|
| Deprecated | 2 |
| Stale | 57 |
| 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 →
get_messages ~65
Fetch recent messages from a specific chat. Use chat_id from list_dialogs or a username like @example.
| Name | Type | Req | Description |
|---|---|---|---|
| chat | string | yes | Chat ID (numeric) or @username |
| limit | number | – | Number of messages to fetch (default 20, max 100) |
No output schema declared.
No examples provided.
list_dialogs ~66
List recent Telegram conversations (DMs, groups, channels). Returns last-message preview, sender, timestamp, and unread count.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Include archived dialogs (default false) |
| limit | number | – | Max dialogs to return (default 30, max 100) |
No output schema declared.
No examples provided.
search_messages ~39
Full-text search across all Telegram conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| query | string | yes | Search query text |
No output schema declared.
No examples provided.
send_message ~51
Send a message to a Telegram chat or user (personal account, not bot).
| Name | Type | Req | Description |
|---|---|---|---|
| chat | string | yes | Chat ID (numeric) or @username |
| text | string | yes | Message text (supports Markdown) |
No output schema declared.
No examples provided.
What is the io.github.auroracapital/claude-ops-telegram-server MCP server?
io.github.auroracapital/claude-ops-telegram-server is an MCP server listed in the public MCP registry as io.github.auroracapital/claude-ops-telegram-server. Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats. This page covers its npm package (claude-ops-telegram-server).
Is the io.github.auroracapital/claude-ops-telegram-server MCP server safe to use?
io.github.auroracapital/claude-ops-telegram-server scores 82 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.auroracapital/claude-ops-telegram-server MCP server expose?
io.github.auroracapital/claude-ops-telegram-server exposes 4 tools: list_dialogs, get_messages, send_message, search_messages. Their descriptions and schemas cost roughly 221 tokens of context every time the server is loaded.
Is the io.github.auroracapital/claude-ops-telegram-server MCP server still maintained?
io.github.auroracapital/claude-ops-telegram-server 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.auroracapital/claude-ops-telegram-server MCP server under?
io.github.auroracapital/claude-ops-telegram-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.