io.github.starnikovoleg/tgatlas
NPM · TGATLAS-MCP · SCANNED SEP 20
Public Telegram channels for agents: profiles, posting cadence, and similar-channel discovery.
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 473 tokens (~157/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.starnikovoleg/tgatlas MCP server?
io.github.starnikovoleg/tgatlas runs locally as an npm package, launched with npx -y tgatlas-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tgatlas-mcp
claude mcp add starnikovoleg-tgatlas -- npx -y tgatlas-mcp
{
"mcpServers": {
"starnikovoleg-tgatlas": {
"command": "npx",
"args": [
"-y",
"tgatlas-mcp"
]
}
}
} {
"servers": {
"starnikovoleg-tgatlas": {
"command": "npx",
"args": [
"-y",
"tgatlas-mcp"
]
}
}
} codex mcp add starnikovoleg-tgatlas -- npx -y tgatlas-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"starnikovoleg-tgatlas": {
"type": "local",
"command": [
"npx",
"-y",
"tgatlas-mcp"
],
"enabled": true
}
}
} openclaw mcp add starnikovoleg-tgatlas --command npx --arg -y --arg tgatlas-mcp
mcp_servers:
starnikovoleg-tgatlas:
command: "npx"
args: ["-y", "tgatlas-mcp"] {
"McpServers": {
"starnikovoleg-tgatlas": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tgatlas-mcp"
]
}
}
} assistant mcp add starnikovoleg-tgatlas -t stdio -c npx -a -y tgatlas-mcp
{
"mcpServers": {
"starnikovoleg-tgatlas": {
"command": "npx",
"args": [
"-y",
"tgatlas-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.
- 19 Sept 26 +1
- Security disclosure: fail → pass ▲ functional
- 17 Sept 26 69
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 npm/tgatlas-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
telegram_channel Telegram channel profile ~163
Look up a public Telegram channel: title, description, exact subscriber count, creation date, verification and scam flags, and how often it posts. Use to check whether a channel is real, how large it is, and whether it is still alive — a channel with 200k subscribers and nothing published this year is a common and invisible failure.
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | boolean | – | Include posting rate and date of the last post. Costs one extra API call. Default true. |
| channel | string | yes | Public channel: @handle, bare handle, or a t.me link. Private channels are not readable. |
| format | string | – | Output shape. "markdown" is compact prose for a model to read; "json" is the raw API response. Default "markdown". |
No output schema declared.
No examples provided.
telegram_search_channels Search public Telegram channels ~98
Telegram's own global search over public channels and groups, by title and handle. Good for seeding a topic; telegram_similar_channels is what expands a seed into a neighbourhood. Short topical words work better than sentences.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output shape. "markdown" is compact prose for a model to read; "json" is the raw API response. Default "markdown". |
| query | string | yes | Keyword to search for. |
No output schema declared.
No examples provided.
telegram_similar_channels Channels Telegram considers similar ~165
Return the channels Telegram itself recommends alongside a given channel — its own topical judgement, not a keyword match, so it surfaces channels that share an audience without sharing vocabulary. The way to discover channels whose names you do not already know: start from one you do and walk outward. Large channels return roughly a dozen; small or very new ones return none.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Public channel: @handle, bare handle, or a t.me link. Private channels are not readable. |
| enrich | boolean | – | Fetch each result’s exact subscriber count. Costs one API call per result. Default false. |
| format | string | – | Output shape. "markdown" is compact prose for a model to read; "json" is the raw API response. Default "markdown". |
No output schema declared.
No examples provided.
What is the io.github.starnikovoleg/tgatlas MCP server?
io.github.starnikovoleg/tgatlas is an MCP server listed in the public MCP registry as io.github.starnikovoleg/tgatlas. Public Telegram channels for agents: profiles, posting cadence, and similar-channel discovery. This page covers its npm package (tgatlas-mcp).
Is the io.github.starnikovoleg/tgatlas MCP server safe to use?
io.github.starnikovoleg/tgatlas scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.starnikovoleg/tgatlas MCP server expose?
io.github.starnikovoleg/tgatlas exposes 3 tools: telegram_channel, telegram_similar_channels, telegram_search_channels. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.
Is the io.github.starnikovoleg/tgatlas MCP server still maintained?
io.github.starnikovoleg/tgatlas 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.starnikovoleg/tgatlas MCP server under?
io.github.starnikovoleg/tgatlas declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.