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/ToruAI/toru-claude-agentsWrote 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/toruai/toru-claude-agents/megg)<a href="https://agentmods.dev/mcp/toruai/toru-claude-agents/megg"><img src="https://agentmods.dev/badge/mcp/toruai/toru-claude-agents/megg/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/toruai/toru-claude-agents/megg"><img src="https://agentmods.dev/badge/mcp/toruai/toru-claude-agents/megg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
megg 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
{
"megg": {
"command": "npx",
"args": [
"-y",
"[email protected]",
"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 · 10 lines scan A 85a7127237f3
megg is an MCP server published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
hex-graph-mcp
Deterministic layered code graph MCP server with framework overlays and SCIP interop. Runs locally from the @levnikolaevich/hex-graph-mcp npm package.
hex-research-mcp
Research graph MCP for hypotheses, goals, runs, source quality, audits, and generated maps. Runs locally from the @levnikolaevich/hex-research-mcp npm package.
hex-line-mcp
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents. Runs locally from the @levnikolaevich/hex-line-mcp npm package.
hex-ssh-mcp
Token-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools. Runs locally from the @levnikolaevich/hex-ssh-mcp npm package.
context-keeper
MCP server that maintains project context (decisions, pipelines, constraints) across Claude conversations. Runs locally from the context-keeper-mcp Python package. Needs 1 environment variable to run.
cctx-optimizer
Reduce Claude Code token usage by 70-90% with cross-session memory and four-layer optimization: semantic codebase indexing, PostToolUse tool compression, turn summarization, and session consolidation. MCP server powered by Ollama — zero API calls, runs en. Runs locally from the cctx-optimizer npm package.