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/ausievich/tg-mcp-toolsWrote 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/ausievich/tg-mcp-tools/tg-mcp)<a href="https://agentmods.dev/mcp/ausievich/tg-mcp-tools/tg-mcp"><img src="https://agentmods.dev/badge/mcp/ausievich/tg-mcp-tools/tg-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/ausievich/tg-mcp-tools/tg-mcp"><img src="https://agentmods.dev/badge/mcp/ausievich/tg-mcp-tools/tg-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tg-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 10d 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
{ "tg-mcp": { "command": "npx", "args": [ "-y", "tg-mcp" ] } }
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.
- 10d ago First seen · 9 lines scan A db5979359b40
tg-mcp is an MCP server published in the GitHub repository ausievich/tg-mcp-tools (1 stars, last pushed 2mo 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
google-suite-mcp
MCP server "google-suite-mcp" as configured in abcreativ/google-suite-mcp. Runs locally from the google-suite-mcp npm package.
veyra-bookmarks
Bookmark and link manager for AI agents with tags, categories, and search. Reads free, writes require Veyra. Runs locally from the veyra-bookmarks npm package.
veyra-forms
Form and survey builder for AI agents. Create forms, collect responses. Reads free, writes require Veyra. Runs locally from the veyra-forms npm package.
veyra-snippets
Code snippet manager with language tags and search for AI agents. Reads free, writes require Veyra. Runs locally from the veyra-snippets npm package.
veyra-contacts
Contact manager for AI agents. Business-critical data — all writes require Veyra. Runs locally from the veyra-contacts npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.