agentmods.dev

telegram-topics

telegram-topics is an MCP server for Claude Code from 2naive/claude-telegram-topics. Its token cost is not measured, scanned A, a copy of whatsapp, Apache-2.0.

A configured MCP server for working with Telegram topics. MCP is a way for an agent to connect to an external tool or service.

In plain words
What is it for?
Use it as the connection setup for Telegram-topic-related agent actions, subject to the server’s actual implementation.
Why use it?
The input only identifies how to start the server; it does not explain which Telegram tasks it supports.

MCP server for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: listed in a Claude config.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the telegram-topics plugin — 3 skills, 4 hooks, 1 MCP server shipped together

not rated 1repo 3d ago A scan tokens not measured copy · 83% Apache-2.0

Good fit Use it as the connection setup for Telegram-topic-related agent actions, subject to the server’s actual implementation.

Compare 6 mcp servers from other repositories ↓
View source ↗ 2naive/claude-telegram-topics
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add 2naive/claude-telegram-topics
Claude Code
/plugin install telegram-topics

Made for: Claude Code.

Or install telegram-topics, the plugin that ships this one along with the rest of its 3 skills, 4 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for telegram-topics

README.md
[![agentmods](https://agentmods.dev/badge/mcp/2naive/claude-telegram-topics/telegram-topics.svg)](https://agentmods.dev/mcp/2naive/claude-telegram-topics/telegram-topics)
Your own site
<a href="https://agentmods.dev/mcp/2naive/claude-telegram-topics/telegram-topics"><img src="https://agentmods.dev/badge/mcp/2naive/claude-telegram-topics/telegram-topics.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

telegram-topics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

83% identical to whatsapp — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.mcp.json · 13 lines

What it actually says

{
  "telegram-topics": {
    "command": "bun",
    "args": [
      "run",
      "--cwd",
      "${CLAUDE_PLUGIN_ROOT}",
      "--shell=bun",
      "--silent",
      "start"
    ]
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 13 lines scan A 579400975a81

Subscribe to this mod's changes

telegram-topics is an MCP server published in the GitHub repository 2naive/claude-telegram-topics (1 stars, last pushed 3d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 83% identical to whatsapp, differing in 2 lines, and is treated as a copy.

Claude Codeanthropicclaude-code-marketplaceclaude-code-pluginclaude-pluginmcp
Related

Other mcp servers, from other repositories

mortgage-pricer

MCP server "mortgage-pricer", hosted remotely at mortgage-pricer-production.up.railway.app, as configured in lendtrain/mortgage.

lendtrain/mortgage · not measured

docs-langchain

MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.

langchain-ai/langchain · not measured

component-explorer

MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.

microsoft/vscode · not measured

vscode-automation-mcp

MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.

microsoft/vscode · not measured

reference-langchain

MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.

langchain-ai/langchain · not measured

supabase

Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.

supabase/supabase · not measured