claude-code-telegrammer
PyPI
v0.6.0
Published by ywatanabe1989 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Custom Telegram MCP server + TUI auto-responder for running Claude Code as an autonomous Telegram agent
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`.claude/skills/skill-creator/eval-viewer/generate_review.py:291`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try: result = subprocess.run( ["lsof", "-ti", f":{port}"], capture_output=True, text=T
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/skill-creator/eval-viewer/generate_review.py
In a packaging/dev/install script (shipped, but not the server runtime) (`docs/to_claude/examples/example-python-project-scitex/scripts/mnist/clf_svm.py:73`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: scitex.io.save(model, eval(CONFIG.PATH.MNIST.MODEL_SVM)) return 0 def parse_args() -> argparse.Namespace: pa
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server docs/to_claude/examples/example-python-project-scitex/scripts/mnist/clf_svm.py
In a packaging/dev/install script (shipped, but not the server runtime) (`docs/to_claude/examples/example-python-project-scitex/scripts/mnist/download.py:41`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: malize( eval(CONFIG.MNIST.NORMALIZE.MEAN), eval(CONFIG.MNIST.NORMALIZE.STD),
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server docs/to_claude/examples/example-python-project-scitex/scripts/mnist/download.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/pptx/scripts/office/soffice.py:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: = get_soffice_env() subprocess.run(["soffice", ...], env=env) """ import os import socket import subprocess import
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/pptx/scripts/office/soffice.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/pptx/scripts/office/validators/redlining.py:138`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: result = subprocess.run( [ "git", "di
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/pptx/scripts/office/validators/redlining.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/pptx/scripts/thumbnail.py:161`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: tem}.pdf" result = subprocess.run( [ "soffice", "--headless", "--conver
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/pptx/scripts/thumbnail.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/skill-creator/scripts/improve_description.py:35`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: UDECODE"} result = subprocess.run( cmd, input=prompt, capture_output=True, text=Tru
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/skill-creator/scripts/improve_description.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/skill-creator/scripts/run_eval.py:85`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: DE"} process = subprocess.Popen( cmd, stdout=subprocess.PIPE, stderr=subpro
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/skill-creator/scripts/run_eval.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/webapp-testing/scripts/with_server.py:69`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: & process = subprocess.Popen( server['cmd'], shell=True, std
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/webapp-testing/scripts/with_server.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/xlsx/scripts/office/soffice.py:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: = get_soffice_env() subprocess.run(["soffice", ...], env=env) """ import os import socket import subprocess import
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/xlsx/scripts/office/soffice.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/xlsx/scripts/office/validators/redlining.py:138`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: result = subprocess.run( [ "git", "di
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/xlsx/scripts/office/validators/redlining.py
In a packaging/dev/install script (shipped, but not the server runtime) (`.claude/skills/xlsx/scripts/recalc.py:34`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: out(): try: subprocess.run( ["gtimeout", "--version"], capture_output=True, timeout=1, check=Fal
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .claude/skills/xlsx/scripts/recalc.py
Each tool and what it can reach — statically extracted from the published source.
download_attachmentingests untrusted inputedit_messageno sensitive capabilityget_contextno sensitive capabilityget_historyno sensitive capabilityget_unreadno sensitive capabilityhealthno sensitive capabilitymark_readno sensitive capabilityreactno sensitive capabilityreplyno sensitive capabilitysearch_messagesno sensitive capabilitysend_documentno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.6.0 latest |
A 93/100 | 12 | 1.13.0 | 2026-08-25 |
v0.5.12 |
A 93/100 | 12 | 1.12.1 | 2026-07-27 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan claude-code-telegrammer --online --registry pypi
Official Abyssfall game info, newsletter double opt-in, and merch reservation tools.
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Google AdSense MCP Server - Monitor earnings, reports, and account health via Claude/AI
Operational empathy for technical founders + PE/VC operators navigating high-stakes B2B interactions. 28 MCP tools + CLI: ICP scoring, persona simulation, battlecards, deal classification, prospect discovery, investor matching, founder wellness, plus mark
MCP server for Bing Webmaster Tools — SEO site management, URL submission, sitemaps, stats, keywords
MCP (Model Context Protocol) server that helps AI agents use Primer Brand (@primer/react-brand) correctly when building GitHub marketing and landing pages.