Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/PrimeUpYourLife/dynamic-telegram-bot-api-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/primeupyourlife/dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp)<a href="https://agentmods.dev/mcp/primeupyourlife/dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp"><img src="https://agentmods.dev/badge/mcp/primeupyourlife/dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/primeupyourlife/dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp"><img src="https://agentmods.dev/badge/mcp/primeupyourlife/dynamic-telegram-bot-api-mcp/dynamic-telegram-bot-api-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
dynamic-telegram-bot-api-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"dynamic-telegram-bot-api-mcp": {
"command": "npx",
"args": [
"-y",
"dynamic-telegram-bot-api-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +3 lines cfafcd516e8e
- 1mo ago First seen · 9 lines scan A 732d41fab51b
dynamic-telegram-bot-api-mcp is an MCP server published in the GitHub repository PrimeUpYourLife/dynamic-telegram-bot-api-mcp (0 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other mcp servers, from other repositories
fast-mcp-telegram
Multi-tenant Telegram gateway for AI agents — HTTP+stdio transport, 8 agent-optimized tools, MTProto User API. Runs locally from the fast-mcp-telegram Python package. Needs 4 environment variables to run.
postman-mcp-server
A basic MCP server to operate on the Postman API. Runs locally from the @postman/postman-mcp-server npm package. Needs 1 environment variable to run.
mcp-server
Model Context Protocol (MCP) server for AI-assisted development of CAP applications. Runs locally from the @cap-js/mcp-server npm package.
telegram-dev
MCP server "telegram-dev" as configured in leshchenko1979/fast-mcp-telegram. Runs src.server with python3.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.
mcp
Apideck Unified API MCP — 330 tools across 200+ SaaS connectors (accounting, CRM, HRIS, ATS). Runs locally from the @apideck/mcp npm package. Needs 3 environment variables to run.