TG multi-account MCP
PYPI · TG-ACCOUNT-MCP · SCANNED SEP 20
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
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 Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 38 of 40 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 38 of 40 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the TG multi-account MCP server?
TG multi-account MCP runs locally as a PyPI package, launched with uvx tg-account-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tg-account-mcp
claude mcp add mesteriis-tg-account-mcp -- uvx tg-account-mcp
{
"mcpServers": {
"mesteriis-tg-account-mcp": {
"command": "uvx",
"args": [
"tg-account-mcp"
]
}
}
} {
"servers": {
"mesteriis-tg-account-mcp": {
"command": "uvx",
"args": [
"tg-account-mcp"
]
}
}
} codex mcp add mesteriis-tg-account-mcp -- uvx tg-account-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mesteriis-tg-account-mcp": {
"type": "local",
"command": [
"uvx",
"tg-account-mcp"
],
"enabled": true
}
}
} openclaw mcp add mesteriis-tg-account-mcp --command uvx --arg tg-account-mcp
mcp_servers:
mesteriis-tg-account-mcp:
command: "uvx"
args: ["tg-account-mcp"] {
"McpServers": {
"mesteriis-tg-account-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"tg-account-mcp"
]
}
}
} assistant mcp add mesteriis-tg-account-mcp -t stdio -c uvx -a tg-account-mcp
{
"mcpServers": {
"mesteriis-tg-account-mcp": {
"command": "uvx",
"args": [
"tg-account-mcp"
]
}
}
} 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
- 18 Sept 26 21
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 20 Sept 2026 · Analysed pypi/tg-account-mcp@0.5.2
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 38 packages
| Packages resolved | 38 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the TG multi-account MCP server?
TG multi-account MCP is listed in the public MCP registry as io.github.Mesteriis/tg-account-mcp. Self-hosted, consent-based access to Telegram accounts and bots for MCP clients. This page covers its PyPI package (tg-account-mcp).
Is the TG multi-account MCP server safe to use?
TG multi-account MCP scores 36 out of 100 on VerifyMCP. 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.
Is the TG multi-account MCP server still maintained?
TG multi-account MCP 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.