io.github.daedalus/mcp-telegram-bot
PYPI · MCP-TELEGRAM-BOT · SCANNED SEP 20
MCP server that exposes a Telegram bot
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 175 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 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
- Tool/resource definitions use about 174 tokens (~43/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 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 current MCP spec version (2026-07-28).Pass
How do I install the io.github.daedalus/mcp-telegram-bot server?
io.github.daedalus/mcp-telegram-bot runs locally as a PyPI package, launched with uvx mcp-telegram-bot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-telegram-bot
claude mcp add daedalus-mcp-telegram-bot -- uvx mcp-telegram-bot
{
"mcpServers": {
"daedalus-mcp-telegram-bot": {
"command": "uvx",
"args": [
"mcp-telegram-bot"
]
}
}
} {
"servers": {
"daedalus-mcp-telegram-bot": {
"command": "uvx",
"args": [
"mcp-telegram-bot"
]
}
}
} codex mcp add daedalus-mcp-telegram-bot -- uvx mcp-telegram-bot
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"daedalus-mcp-telegram-bot": {
"type": "local",
"command": [
"uvx",
"mcp-telegram-bot"
],
"enabled": true
}
}
} openclaw mcp add daedalus-mcp-telegram-bot --command uvx --arg mcp-telegram-bot
mcp_servers:
daedalus-mcp-telegram-bot:
command: "uvx"
args: ["mcp-telegram-bot"] {
"McpServers": {
"daedalus-mcp-telegram-bot": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-telegram-bot"
]
}
}
} assistant mcp add daedalus-mcp-telegram-bot -t stdio -c uvx -a mcp-telegram-bot
{
"mcpServers": {
"daedalus-mcp-telegram-bot": {
"command": "uvx",
"args": [
"mcp-telegram-bot"
]
}
}
} 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 +15
- Malware scan: unverified → pass ▲ security
- 19 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 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 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 20 Sept 2026 · Analysed pypi/mcp-telegram-bot@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 1 |
| 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_me Get Me ~30
Get bot information. Returns: JSON response containing bot information (id, username, first_name, etc.).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_updates Get Updates ~57
Get recent updates from Telegram.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of updates to return (1-100). Defaults to 10. |
| offset | – | – | Identifier of the first returned update. Only updates with id greater than offset are returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
send_message Send Message ~57
Send a message to a specified Telegram chat.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | The Telegram chat ID to send the message to. Can be a numeric ID or username with @ prefix. |
| text | string | yes | The message text to send. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.daedalus/mcp-telegram-bot server?
io.github.daedalus/mcp-telegram-bot is listed in the public MCP registry as io.github.daedalus/mcp-telegram-bot. MCP server that exposes a Telegram bot. This page covers its PyPI package (mcp-telegram-bot).
Is the io.github.daedalus/mcp-telegram-bot server safe to use?
io.github.daedalus/mcp-telegram-bot scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.daedalus/mcp-telegram-bot server expose?
io.github.daedalus/mcp-telegram-bot exposes 3 tools: send_message, get_me, get_updates. Their descriptions and schemas cost roughly 144 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-telegram-bot server still maintained?
io.github.daedalus/mcp-telegram-bot 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.daedalus/mcp-telegram-bot server under?
io.github.daedalus/mcp-telegram-bot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.