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/MediaZione/AwrAiterWrote 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/mediazione/awraiter/telegram)<a href="https://agentmods.dev/mcp/mediazione/awraiter/telegram"><img src="https://agentmods.dev/badge/mcp/mediazione/awraiter/telegram/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/mediazione/awraiter/telegram"><img src="https://agentmods.dev/badge/mcp/mediazione/awraiter/telegram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
telegram 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
{
"telegram": {
"url": "https://awraiter.ai/mcp",
"type": "streamable-http"
}
}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 First seen · 6 lines scan A 9be4ed04f11c
telegram is an MCP server published in the GitHub repository MediaZione/AwrAiter (0 stars, last pushed 9d 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
graphmind
MCP server "graphmind" as configured in aouicher/graphmind. Launched with graphmind mcp.
klaviyo
MCP server "klaviyo", hosted remotely at mcp.klaviyo.com, as configured in minhnv0807/ai-business-skills.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
mcp-ads
MCP server "mcp-ads", hosted remotely at mcp-ads.com, as configured in RoyAzran/mcp-ads.
meetmyagent
MCP server "meetmyagent", hosted remotely at meetmyagent.io, as configured in studiomeyer-io/meetmyagent-mcp.
socials
MCP server "socials" as configured in aryaminus/socials-assistant. Runs ${workspaceFolder}/apps/mcp/bin/socials-mcp.js with node. Needs 1 environment variable to run.