telegram-account-orchestrator (soulknight666/telegram-account-orchestrator) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

D
Caution
54/100
24 days ago

telegram-account-orchestrator

MCP server for self-hosted Telegram multi-account management, enabling encrypted session storage, health checks, batch operations, device-session management, and automation through AI agents.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

soulknight666

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: TAM_BOT_TOKEN, BOT_TOKEN, OKPAY_TOKEN, TAM_MASTER_KEY, TAM_WEB_TOKEN, TAM_READONLY_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configTAM_API_ID
configTELEGRAM_APP_ID
configTAM_API_HASH
configTELEGRAM_APP_HASH
configTAM_TOAPI_BASE转 API 相关环境变量:(优先)、DM、SERVER_IP/API_PORT。
configDM转 API 相关环境变量:TAM_TOAPI_BASE(优先)、、SERVER_IP/API_PORT。
configSERVER_IP转 API 相关环境变量:TAM_TOAPI_BASE(优先)、DM、/API_PORT。
configAPI_PORT转 API 相关环境变量:TAM_TOAPI_BASE(优先)、DM、SERVER_IP/。
configTAM_DATA_DIR
configNO_COLOR
configWT_SESSION
configTERM_PROGRAM
configTAM_RESTARTED_AT
config_TAM_DUR_PROBE
configTAM_ENV_FILE
🔐 secretTAM_BOT_TOKEN选了机器人但还没有 Token:会提示填一次 @BotFather 的 (可回车跳过,稍后写 .env)。
🔐 secretBOT_TOKEN
configTAM_BOT_ADMIN_ID
configADMIN_ID
configSTART_JOIN_USERNAME
configOKPAY_ID填了 / OKPAY_TOKEN / OKPAY_COST 才会开付费门槛:下单后每 5 秒轮询,5 分钟不付自动关单,
🔐 secretOKPAY_TOKEN填了 OKPAY_ID / / OKPAY_COST 才会开付费门槛:下单后每 5 秒轮询,5 分钟不付自动关单,
configOKPAY_PAYED
configOKPAY_COST留空就是不收费,任何人进来直接是 VIP(自用场景默认这样)。
configTAM_PORT
🔐 secretTAM_MASTER_KEYpython -m tam.cli init-key # 生成 ,写入 .env
🔐 secretTAM_WEB_TOKEN所有 /api/ 需 Authorization: Bearer <>。若向导里选了“本机免令牌”(TAM_NO_AUTH=1 且 TAM_WEB_TOKEN 为空),则不需要任何头部,直接访问即可。
configTAM_DEFAULT_PROXY
configTAM_READONLY1 或使用 TAM_READONLY_TOKEN 时,写入类工具从清单中消失并被拒绝——推荐给 Agent 单独发只读令牌。
configTAM_DRY_RUN1 全局干跑;TAM_PEER_ALLOWLIST 限定可发送对象。
🔐 secretTAM_READONLY_TOKENTAM_READONLY=1 或使用 时,写入类工具从清单中消失并被拒绝——推荐给 Agent 单独发只读令牌。
configTAM_PEER_ALLOWLISTTAM_DRY_RUN=1 全局干跑; 限定可发送对象。
configTAM_NO_AUTH所有 /api/ 需 Authorization: Bearer <TAM_WEB_TOKEN>。若向导里选了“本机免令牌”(=1 且 TAM_WEB_TOKEN 为空),则不需要任何头部,直接访问即可。
configTAM_BATCH_CONCURRENCY3 工具箱、批量任务同时开几个号;调大易触频控
configTAM_DEPLOYpython -m tam.cli run # 读 .env 里的 / TAM_FRONTEND
configTAM_FRONTENDpython -m tam.cli run # 读 .env 里的 TAM_DEPLOY /
configTAM_NO_MENU
configTAM_HOST
configTAM_PROXY_FILE
configTAM_WORKERS4 ZIP 拆包 / 合并 / 注册时间分类的并发度,上限 32
configTAM_KICK_RETRY1h 失败后的重试间隔,支持秒/分/时写法:45s、10m、2h、1h30m,纯数字按秒,最小 10 秒。
configUNPACK_TOOL_BACK
configMK_TIME
configMK_LIST_TIME
configPREVENT_RECOVERY_BACK
configFORMAT_CONVERT_BACK
configPASSKEY_BACK
configOKPAY_RETURN_URL
configCLEAN_ACCOUNT_BACK
configCHECK_BAN_BACK
configSHAIHUO_BACK
configCHECK_MATERIAL_BACK
configTEST_BIDIRECTIONAL_BACK
configDESTROY_BACK
configCHANGE_2FA_BACK
configPRIVACY_CONFIG_BACK
configCONVERT_API_BACK
configTAM_MAX_EXTRACT_MB512 解压后总大小上限,防 zip 炸弹
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

73/73 tools missing one or more hints — _list_settings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); _update_settings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); _list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +70 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — _zip_merge deletes at line 703 (shutil.rmtree(src, ignore_errors=True)); _zip_cleanup deletes at line 759 (shutil.rmtree(d, ignore_errors=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

70/73 tool handlers declare input schemas (96%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 7/73 tool handlers wrap calls in try/catch (10%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

2 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/soulknight666-telegram-account-orchestrator-1b0vvc?variant=verified)](https://m8ven.ai/mcp/soulknight666-telegram-account-orchestrator-1b0vvc)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f46f60fe3029fe285e50d3235abf6ebbc8069bfe
code hash: 0039eb32d34bec04d90c68cdf42b7361182dc859fb1dd6ba5b18ad66d88be0cb
verified: 8/3/2026, 10:19:39 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client