Remote MCP · Endpoint
io.github.leshchenko1979/fast-mcp-telegram MCP server
No. io.github.leshchenko1979/fast-mcp-telegram answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://tg-mcp.l1979.ru/v1/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.leshchenko1979/fast-mcp-telegram
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 282 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 282 ms |
| 1 day ago | Handshake completed | 270 ms |
| 2 days ago | Handshake completed | 268 ms |
| 3 days ago | Handshake completed | 273 ms |
| 4 days ago | Handshake completed | 275 ms |
| 5 days ago | Handshake completed | 274 ms |
| 6 days ago | Handshake completed | 302 ms |
| 9 days ago | Handshake completed | 340 ms |
| 11 days ago | Handshake completed | 755 ms |
| 14 days ago | Handshake completed | 276 ms |
| 16 days ago | Handshake completed | 328 ms |
| 18 days ago | Handshake completed | 264 ms |
| 20 days ago | Handshake completed | 318 ms |
| 22 days ago | Handshake completed | 264 ms |
| 24 days ago | Handshake completed | 290 ms |
| 26 days ago | Handshake completed | 299 ms |
| 27 days ago | Handshake completed | 278 ms |
| 29 days ago | Handshake completed | 265 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with io.github.leshchenko1979/fast-mcp-telegram and makes no claim about it beyond what these checks measured.