Skip to content
Back to search

mcp-telegram-channels

telegram-channels: public Telegram channels through Telegram's public web preview. Live keyless proxy. Public channels only; nothing behind a login.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeworx-io--mcp-telegram-channels/badge.svg)](/listings/pipeworx-io--mcp-telegram-channels)

HTML

<a href="/listings/pipeworx-io--mcp-telegram-channels"><img src="/api/listings/pipeworx-io--mcp-telegram-channels/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "telegram-channels": {
      "url": "https://gateway.pipeworx.io/telegram-channels/mcp"
    }
  }
}

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/telegram-channels/mcp` returns the tools in the table above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`, `discover_tools`, `search_within`, `remember`/`recall` and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's `initialize` response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via `ask_pipeworx`, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 2034+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 129 lines
  1. # @pipeworx/telegram-channels
  2. Public Telegram channels: profile (title, description, subscribers, media counts) and recent posts with date, text and view count. Live and keyless; public channels only.
  3. Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
  4. ## Tools
  5. - `telegram_channel(channel)` — title, username, verified flag, description, subscriber count, photo, video and link counts.
  6. - `telegram_channel_posts(channel, limit?, before_id?)` — recent posts, newest first: post id and link, date, text, views, and whether it carries photo, video or a link preview. Page back with `before_id`.
  7. ## Auth
  8. Keyless.
  9. ## Data sources
  10. - Telegram, public channel web preview. Only what the public page shows to anyone without an account: no private channels, no groups, no member lists, no user profiles.
  11. Gotchas: a name that is not a public channel (private, group, user, bot, missing) is reported as an error rather than an empty result. Counts such as "9.91M" are rounded by the source; the tool converts them to integers and they stay approximate. Each page carries about 20 posts; reactions and media files are not returned.
  12. ## Quick Start
  13. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  14. ```json
  15. {
  16. "mcpServers": {
  17. "telegram-channels": {
  18. "url": "https://gateway.pipeworx.io/telegram-channels/mcp"
  19. }
  20. }
  21. }
  22. ```
  23. ### What this endpoint actually serves
  24. `tools/list` at `https://gateway.pipeworx.io/telegram-channels/mcp` returns the tools in the table
  25. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  26. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  27. gateway-wide set. So the tool count you see is larger than this table: a
  28. single-pack endpoint currently lists roughly 30 shared tools alongside the
  29. pack's own. The connection's `initialize` response states its exact scope, and
  30. is the authoritative answer for a given day.
  31. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  32. scoped connection answer a question this pack does not cover — via
  33. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  34. second MCP server. There is currently no way to mount a pack endpoint without
  35. them; if the extra schemas cost you more context than the routing is worth,
  36. connect to the full gateway once rather than to several pack endpoints.
  37. Or connect to the full Pipeworx gateway to get every pack's tools listed
  38. directly, instead of just this one's:
  39. ```json
  40. {
  41. "mcpServers": {
  42. "pipeworx": {
  43. "url": "https://gateway.pipeworx.io/mcp"
  44. }
  45. }
  46. }
  47. ```
  48. Both URLs reach the same gateway and the same 2034+ data sources. The
  49. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  50. reaches all of them from either one.
  51. ## No MCP client? Call it over HTTP
  52. ```bash
  53. curl -X POST https://gateway.pipeworx.io/v1/tools/telegram_channel \
  54. -H 'Content-Type: application/json' \
  55. -d '{"channel":"durov"}'
  56. ```
  57. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/telegram_channel`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  58. ## Run it from npm
  59. `@pipeworx/mcp-telegram-channels` is a local stdio bridge to the Pipeworx gateway: your MCP client
  60. starts it with `npx`, and it forwards every call to the same
  61. `https://gateway.pipeworx.io/telegram-channels/mcp` endpoint shown above. It needs network access;
  62. there is no offline mode.
  63. ```json
  64. {
  65. "mcpServers": {
  66. "telegram-channels": {
  67. "command": "npx",
  68. "args": ["-y", "@pipeworx/mcp-telegram-channels"]
  69. }
  70. }
  71. }
  72. ```
  73. Without a key it calls anonymously, capped at 50 calls a day. A free account
  74. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  75. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  76. The key is sent as a Bearer token, the same way a hosted connection sends it,
  77. so calls are metered and billed exactly as they are there.
  78. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  79. also list `ask_pipeworx` and the other gateway-wide tools.
  80. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  81. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  82. your Node version's documentation.
  83. ## Using with ask_pipeworx
  84. Instead of calling tools directly, you can ask questions in plain English —
  85. this works on the pack endpoint above as well as on the full gateway:
  86. ```
  87. ask_pipeworx({ question: "your question about Telegram Channels data" })
  88. ```
  89. The gateway picks the right tool and fills the arguments automatically.
  90. ## More
  91. - [Docs and guides](https://pipeworx.io/docs)
  92. - [pipeworx.io](https://pipeworx.io)
  93. ## License
  94. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.