MCPLow riskUnclaimed

telegram-mcp

Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.

Shreyas-Profileshreyas-profile/telegram-mcpUpdated Jul 14, 2026

server.json

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "name": "io.github.Shreyas-Profile/telegram-mcp",
  "description": "Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.",
  "repository": {
    "url": "https://github.com/globalion/telegram-mcp",
    "source": "github"
  },
  "version": "0.4.0",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://telegram.regiq.in/api/mcp",
      "headers": [
        {
          "description": "Bearer <apiKey> — get yours at https://telegram.regiq.in after Google sign-in.",
          "name": "Authorization"
        }
      ]
    }
  ]
}

Permissions

DeclaredDetected
Runs code—None
Installs—None
Runs install scripts—None
Networktelegram.regiq.intelegram.regiq.in
Needs credentialsNoneNone
Outside the workspace—None
Agent tools—None

Checks

Low risk · Nothing worth a warning was found.

Not reviewed by a person · Checked by rules; the model review is not switched on yet.

Versions

  1. #10.4.0latestOct 7, 2026