telegram-mcp-readonly (mshykhov/telegram-mcp-readonly) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 129 tools. No publisher has claimed this listing.

D
Caution
58/100

telegram-mcp-readonly

Read-only Telegram MCP server. Search chats, read messages, and download attachments from any MCP client.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

mshykhov

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GROQ_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool annotations don’t match behaviour
1 read-only tool performs write/delete/exec — open_photo (line 737: kept_path.write_bytes(photo_bytes))
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — open_photo (line 737: kept_path.write_bytes(photo_bytes))
🔐
You'll be asked for 1 credential: GROQ_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configXDG_STATE_HOME
configTELEGRAM_EVENT_FEED
configTELEGRAM_READONLY_DOWNLOAD_DIR
configTELEGRAM_LINK_DOMAIN
🔐 secretGROQ_API_KEY
configTELEGRAM_API_ID
configTELEGRAM_API_HASH
configTELEGRAM_LOCK_GRACE_SECONDS
configTELEGRAM_SESSION_LOCK
configMCP_ALLOWED_HOSTS
configMCP_ALLOWED_ORIGINS
configMCP_HOST
configMCP_PORT
configMCP_TRANSPORT
configTELEGRAM_EXPOSED_TOOLS
configTELEGRAM_FLOOD_SLEEP_THRESHOLD
configTELEGRAM_SESSION_STRINGS
configTELEGRAM_SESSION_STRING
configTELEGRAM_SESSION_NAME
configTELEGRAM_CONTACT_FUZZY
configTELEGRAM_ALLOW_SERVER_ROOTS_FALLBACK
configXDG_DATA_HOME
configTELEGRAM_TRANSCRIBE
configTELEGRAM_TRANSCRIBE_ENGINE
configTELEGRAM_TRANSCRIBE_GROQ_MAX_MB
configTELEGRAM_TRANSCRIPT_CACHE_DIR
configTELEGRAM_TRANSCRIBE_MAX_VOICES
configTELEGRAM_TRANSCRIBE_MAX_SECONDS
// quality suggestions

All four hints declared on every tool

129/129 tools missing one or more hints — list_accounts (missing: destructiveHint, idempotentHint, openWorldHint); get_chats (missing: destructiveHint, idempotentHint); subscribe_public_channel (missing: readOnlyHint), +126 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool annotations match behaviour

1 read-only tool performs write/delete/exec — open_photo (line 737: kept_path.write_bytes(photo_bytes))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — open_photo (line 737: kept_path.write_bytes(photo_bytes))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

60/129 tools referenced in tests (47%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

open_photo: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/mshykhov/telegram-mcp-readonly?variant=verified)](https://m8ven.ai/mcp/mshykhov/telegram-mcp-readonly)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 85fe361402c0393c8a90d3eb6959ca433ea1ed5e
code hash: a08aae41fc0dd3c6e4cdf981bbe2b0e4905f44a74aab10de61eeaddd50c619be
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client