Remote MCP · Endpoint

io.telemost/telemost-mcp-server MCP server

No. io.telemost/telemost-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.telemost.io/mcp

The last check completed an MCP handshake.

Registry name
io.telemost/telemost-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
165 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Telegram channel analytics and statistics for AI agents, pay-per-call in USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of io.telemost/telemost-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed165 ms
2 days agoHandshake completed165 ms
4 days agoHandshake completed307 ms
6 days agoHandshake completed144 ms
7 days agoHandshake completed162 ms
9 days agoHandshake completed151 ms
10 days agoHandshake completed158 ms
11 days agoHandshake completed337 ms
14 days agoHandshake completed301 ms
15 days agoHandshake completed192 ms
17 days agoHandshake completed147 ms
19 days agoHandshake completed139 ms
20 days agoHandshake completed314 ms
21 days agoHandshake completed209 ms
22 days agoHandshake completed153 ms
22 days agoHandshake completed140 ms
23 days agoHandshake completed160 ms
25 days agoHandshake completed140 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.

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.telemost/telemost-mcp-server and makes no claim about it beyond what these checks measured.