dynamic-telegram-bot-api-mcp

MCPattested
v10.3.3io.github.patricktobias86MITUpdated 23d agonpmGitHub

A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API

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.
427Downloads/wk
23d agoLast update
Needs 1 credential before it runs
  • TELEGRAM_BOT_TOKENAPI keyrequired

    Telegram Bot API token from @BotFather

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.patricktobias86
LicenseMIT
Version10.3.3
Sourcenpm+mcp-registry
npmdynamic-telegram-bot-api-mcp
GitHubPrimeUpYourLife/dynamic-telegram-bot-api-mcp
SBOMCycloneDX 1.6 ↓
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 · c289ca8
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv10.3.4 · 21d agoHow well does this scan work?
EvalsNone
IndexedSep 12, 2026

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

Tools

5 tools · none privileged
Statically extracted from the published packagev10.3.4 · 21d 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.

telegram_call_methodValidate and execute any current Telegram Bot API method. Destructive methods require confirm=true. Local files and base64 upload descriptors are converted to multipart uploads.

Validate and execute any current Telegram Bot API method. Destructive methods require confirm=true. Local files and base64 upload descriptors are converted to multipart uploads.

No input schema was published for this tool.

telegram_get_methodReturn the complete current schema for one Telegram Bot API method.

Return the complete current schema for one Telegram Bot API method.

No input schema was published for this tool.

telegram_get_typeReturn the complete current definition of a Telegram Bot API object or union type.

Return the complete current definition of a Telegram Bot API object or union type.

No input schema was published for this tool.

telegram_refresh_schemaFetch and atomically install the latest schema from the official Telegram Bot API documentation.

Fetch and atomically install the latest schema from the official Telegram Bot API documentation.

No input schema was published for this tool.

telegram_search_methodsFuzzy-search every Telegram Bot API method by name, description, category, or parameter name.

Fuzzy-search every Telegram Bot API method by name, description, category, or parameter name.

No input schema was published for this tool.

5 of 5 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

A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

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

60 packages resolved · 3 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

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

+44 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