# io.github.starnikovoleg/tgatlas (npm · tgatlas-mcp)

Public Telegram channels for agents: profiles, posting cadence, and similar-channel discovery.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `tgatlas-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp.md), [page](https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp)

## Channel facts

- Registry: `npm`
- Package: `tgatlas-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add starnikovoleg-tgatlas -- npx -y tgatlas-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "starnikovoleg-tgatlas": {
      "command": "npx",
      "args": [
        "-y",
        "tgatlas-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "starnikovoleg-tgatlas": {
      "command": "npx",
      "args": [
        "-y",
        "tgatlas-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add starnikovoleg-tgatlas -- npx -y tgatlas-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "starnikovoleg-tgatlas": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tgatlas-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add starnikovoleg-tgatlas --command npx --arg -y --arg tgatlas-mcp
```

### Hermes

```yaml
mcp_servers:
  starnikovoleg-tgatlas:
    command: "npx"
    args: ["-y", "tgatlas-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "starnikovoleg-tgatlas": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tgatlas-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add starnikovoleg-tgatlas -t stdio -c npx -a -y tgatlas-mcp
```

### Other

```json
{
  "mcpServers": {
    "starnikovoleg-tgatlas": {
      "command": "npx",
      "args": [
        "-y",
        "tgatlas-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 70, +1)

- [functional improvement] Security disclosure: fail → pass

### 2026-09-17 (score 69)

First indexed and scored.

## MCP tools (3)

### `telegram_channel` (~163 tokens)

Telegram channel profile

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.

Input parameters:

- `cadence` (boolean): Include posting rate and date of the last post. Costs one extra API call. Default true.
- `channel` (string, required): 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".

### `telegram_similar_channels` (~165 tokens)

Channels Telegram considers similar

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.

Input parameters:

- `channel` (string, required): 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".

### `telegram_search_channels` (~98 tokens)

Search public Telegram channels

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.

Input parameters:

- `format` (string): Output shape. "markdown" is compact prose for a model to read; "json" is the raw API response. Default "markdown".
- `query` (string, required): Keyword to search for.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/tgatlas-mcp
- Socket report: https://socket.dev/npm/package/tgatlas-mcp
- Repository: https://github.com/starnikovoleg/tgatlas-mcp
- Website: https://tgatlas.org/
- Changelog RSS feed: https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp.json
- HTML version of this page: https://verifymcp.io/servers/starnikovoleg-tgatlas/tgatlas-mcp