Robin Saige we check the tools AI agents call

fast mcp telegram

io.github.leshchenko1979/fast-mcp-telegram

Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API

— the operator's own registry description reported

Publisher io.github.leshchenko1979 · first seen 2026-08-12 · endpoint https://tg-mcp.l1979.ru/v1/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
8
tools served

Dependency rating derived

allow — mid-slow-solo — safe to depend on

Cluster mid-slow-solo · distinctiveness 0.615 (unusual). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency707 ms
vs populationslow
protocolcurrent
authopen
Use — can it use it?
tools8
vs populationmid
capabilities6
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_b4cd1186e2d2ac2ccf228bb3 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

edit_message find_chats get_chat_info get_messages invoke_mtproto search_messages_globally send_message send_message_to_phone

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific8/8
has a description8/8
description is substantive8/8
parameters are typed8/8
parameters are described8/8

8 of 8 tools graded · 8 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
3.4.3
server version Telegram MCP Server

Capabilities: experimental extensions logging prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:44Zok_tools2007072025-06-18
2026-08-12T05:34:56Zok_tools2006162025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.leshchenko1979/fast-mcp-telegram.svg)](https://robinsaige.com/s/io.github.leshchenko1979/fast-mcp-telegram)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview