Developer · Remote MCP server
Telegram MCP
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Shreyas-Profile/telegram-mcp- Version
- 0.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-14
- Updated
- 2026-07-14
- Publisher
- Shreyas-Profile (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Shreyas-Profile) · how
- Listed under
- Telegram MCP servers
- Repository
- github.com/globalion/telegram-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://telegram.regiq.in/api/mcp | Authorization |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Telegram MCP
Telegram MCP is a remote MCP server: there is nothing to install. Its endpoint is https://telegram.regiq.in/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Shreyas-Profile (GitHub)
| Server | Runs |
|---|---|
| Browser MCPHosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot. | Remote · HTTPLive check: ✓ handshake |
| Cron MCPCron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL. | Remote · HTTPLive check: ✗ no handshake |
| Docs MCPVector RAG store for Word/Excel/PDF/PowerPoint. Break-even pricing, $5 per 5,700 pages. | Remote · HTTPLive check: ✗ no handshake |
| Tor MCPRoute HTTP requests through the Tor network. Rotating exit IPs,.onion support, no body logging. | Remote · HTTPLive check: ✗ no handshake |
More developer servers
| Server | Runs |
|---|---|
| Tech Debt MCPMCP Server for analyzing technical debt across multiple programming languages. | Local · stdio |
| Tech Stack DetectorDetect the technology stack behind any website: frameworks, CMS, analytics, and more from one POST. | Remote · HTTPLive check: ✓ handshake |
| Technology Stack Detection APIDetect 50+ technologies on any website: CMS, frameworks, analytics, CDN. x402. | Remote · SSELive check: ✗ no handshake |
| TelbaseDeploy any web project with one command. AI-native platform with self-healing feedback. | Local · stdio |
| TelegraphDecentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments. | Local · stdio |
| telleroutlook MCP-SERVERWasmAgent MCP server - WASM-sandboxed code execution with capability manifests and Tasks API. | Local · stdio |
| Telys - on-device memoryPrivate on-device memory & retrieval for AI assistants - offline vector + lexical search. | Local · stdio |
| TemperaPersistent episodic memory for AI coding: capture, retrieve, brief, dream cycle, cross-project. | Local · stdio |