MCP server for Telegram: datacenter detection, account age estimation, user/chat lookup
SaferSkills independently audited Tg Id Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
MCP server for Telegram user/chat lookup with datacenter detection and account age estimation.
Works with Claude Code, Claude Desktop, and any MCP-compatible client.
| Tool | Description |
|---|---|
user_info | Look up any user, group, or channel by @username or numeric ID |
dc_detect | Detect which Telegram datacenter (DC1-DC5) hosts an account |
estimate_age | Estimate when an account was created based on its ID |
send_message | Send a message via your Telegram bot |
check_membership | Check if a user is a member/admin/banned in a chat |
get_me | Verify bot connection and capabilities |
dc_map | Get the full datacenter location map |
Telegram assigns each account to one of 5 datacenters at registration. This server extracts the DC from the user's profile photo file_id — a technique not available through the standard Bot API.
| DC | Location | Typical regions |
|---|---|---|
| DC1 | Miami, USA | Early accounts, Americas |
| DC2 | Amsterdam, NL | Europe, CIS |
| DC3 | Miami, USA | Americas (expansion) |
| DC4 | Amsterdam, NL | Europe (expansion) |
| DC5 | Singapore, SG | Asia-Pacific |
Telegram IDs are assigned roughly sequentially. Using known reference points (2013–2025), this server estimates when an account was created with ±2-3 month accuracy, and assigns a badge:
claude mcp add tg-id-mcp -e TELEGRAM_BOT_TOKEN=YOUR_TOKEN -- uvx tg-id-mcpAdd to claude_desktop_config.json:
{
"mcpServers": {
"tg-id-mcp": {
"command": "uvx",
"args": ["tg-id-mcp"],
"env": {
"TELEGRAM_BOT_TOKEN": "YOUR_BOT_TOKEN"
}
}
}
}git clone https://github.com/barkoszloy/tg-id-mcp.git
cd tg-id-mcp
uv run tg-id-mcp/newbot and follow the prompts123456789:ABCdefGHIjklMNO...)Once connected, ask Claude:
Datacenter detection decodes the base64 file_id from a user's profile photo. Byte 4 in the decoded structure contains the DC number (1-5). This works because Telegram stores files on the same DC as the account.
Age estimation uses a lookup table of 41 known ID→date reference points, collected from public research and early account screenshots. The table maps ID ranges to approximate registration months from August 2013 to December 2024.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.