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/laser54/telegram-managed-bot-factoryWrote 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/laser54/telegram-managed-bot-factory/bot-factory)<a href="https://agentmods.dev/mcp/laser54/telegram-managed-bot-factory/bot-factory"><img src="https://agentmods.dev/badge/mcp/laser54/telegram-managed-bot-factory/bot-factory/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/laser54/telegram-managed-bot-factory/bot-factory"><img src="https://agentmods.dev/badge/mcp/laser54/telegram-managed-bot-factory/bot-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bot-factory 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 9d 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
{
"bot-factory": {
"command": "uvx",
"args": [
"telegram-managed-bot-factory"
],
"env": {}
}
}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.
- 9d ago First seen · 9 lines scan A a1c7a238059c
bot-factory is an MCP server published in the GitHub repository laser54/telegram-managed-bot-factory (0 stars, last pushed 3d 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-08-31.
Other mcp servers, from other repositories
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
openpost
Manage social publishing workflows through OpenPost. Remote server at app.openpost.social.
brave-search
Lets the agent search the web and local businesses through the Brave Search API. Runs locally from the @modelcontextprotocol/server-brave-search npm package. Needs 1 environment variable to run.
zotero
MCP server "zotero" as configured in scitex-ai/scitex-python. Launched with mcp-zotero. Needs 2 environment variables to run.
windows-operations-mcp
MCP server "windows-operations-mcp" as configured in sandraschi/windows-operations-mcp. Runs locally from the windows-operations-mcp Python package.
yaml-workflow
A lightweight workflow engine for CI/CD pipelines, data processing, and DevOps automation — define tasks in YAML, run anywhere. Runs locally from the yaml-workflow Python package.