telegram-slack-mcp

MCPattested
v0.5.1io.github.nileshpatil6UnknownUpdated 1mo agonpmGitHub

Read and reply to your personal Telegram chats and all your Slack workspaces.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1mo agoLast update
Reads these credentials
  • TELEGRAM_API_HASHAPI keyoptional

    api_hash from https://my.telegram.org (Telegram server only)

  • SLACK_USER_TOKENSAPI keyoptional

    One Slack user token (xoxp-) per workspace, comma separated (Slack server only)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.nileshpatil6
LicenseUnknown
Version0.5.1
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · e032a88
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · none privileged
Security scan✓ Cleanv0.5.1 · 23d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · none privileged
Statically extracted from the published packagev0.5.1 · 23d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

loginPrompt for your Slack user tokens and save them, so they do not have to live in the

Prompt for your Slack user tokens and save them, so they do not have to live in the

No input schema was published for this tool.

whoamiList every connected Slack workspace and who you are in each.

List every connected Slack workspace and who you are in each.

No input schema was published for this tool.

list_channelsList channels across all connected workspaces, or just one.

List channels across all connected workspaces, or just one.

No input schema was published for this tool.

list_dmsList your direct-message conversations (1:1 and group DMs).

List your direct-message conversations (1:1 and group DMs).

No input schema was published for this tool.

read_channelRead recent messages of a channel or DM. `channel` accepts an id, #name, or part of a name.

Read recent messages of a channel or DM. `channel` accepts an id, #name, or part of a name.

No input schema was published for this tool.

read_threadRead the replies of one thread. `thread_ts` is the parent message's ts.

Read the replies of one thread. `thread_ts` is the parent message's ts.

No input schema was published for this tool.

search_messagesSearch messages across every connected workspace. Supports Slack modifiers like in:#channel and from:@user.

Search messages across every connected workspace. Supports Slack modifiers like in:#channel and from:@user.

No input schema was published for this tool.

unread_summaryShow channels and DMs with unread messages, across all workspaces.

Show channels and DMs with unread messages, across all workspaces.

No input schema was published for this tool.

read_fileDownload a file shared in Slack and return it, so images can actually be seen rather

Download a file shared in Slack and return it, so images can actually be seen rather

No input schema was published for this tool.

send_messagePost a message as yourself. Set thread_ts to reply in a thread. Disabled unless SLACK_ALLOW_SEND=1.

Post a message as yourself. Set thread_ts to reply in a thread. Disabled unless SLACK_ALLOW_SEND=1.

No input schema was published for this tool.

login_statusCheck whether the QR from `login` has been scanned yet. Call this after telling the

Check whether the QR from `login` has been scanned yet. Call this after telling the

No input schema was published for this tool.

login_startStep 1 of login: send a Telegram login code to a phone number in international format (e.g. +9198...).

Step 1 of login: send a Telegram login code to a phone number in international format (e.g. +9198...).

No input schema was published for this tool.

login_completeStep 2 of login: submit the code Telegram sent, plus the cloud password if the account has 2FA.

Step 2 of login: submit the code Telegram sent, plus the cloud password if the account has 2FA.

No input schema was published for this tool.

list_chatsList recent chats (DMs, groups, channels), newest activity first, with unread counts.

List recent chats (DMs, groups, channels), newest activity first, with unread counts.

No input schema was published for this tool.

read_chatRead the most recent messages of one chat. `chat` accepts @username, numeric id, or part of the chat name.

Read the most recent messages of one chat. `chat` accepts @username, numeric id, or part of the chat name.

No input schema was published for this tool.

read_mediaDownload the media attached to one message and return it, so images can actually be

Download the media attached to one message and return it, so images can actually be

No input schema was published for this tool.

16 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read and reply to your personal Telegram chats and all your Slack workspaces.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-20 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in chat & messaging