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/joshrotenberg/tower-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/joshrotenberg/tower-mcp/codegen-mcp)<a href="https://agentmods.dev/mcp/joshrotenberg/tower-mcp/codegen-mcp"><img src="https://agentmods.dev/badge/mcp/joshrotenberg/tower-mcp/codegen-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/joshrotenberg/tower-mcp/codegen-mcp"><img src="https://agentmods.dev/badge/mcp/joshrotenberg/tower-mcp/codegen-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codegen-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
{
"codegen-mcp": {
"command": "cargo",
"args": [
"run",
"-p",
"codegen-mcp"
],
"env": {
"RUST_LOG": "codegen_mcp=info"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 13 lines scan A a48ec55d15c3
codegen-mcp is an MCP server published in the GitHub repository joshrotenberg/tower-mcp (11 stars, last pushed today), licensed Apache-2.0. 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
tokio-prompt-orchestrator
MCP server "tokio-prompt-orchestrator" as configured in Mattbusel/tokio-prompt-orchestrator. Launched with cargo run --bin mcp --features mcp --release. Needs 3 environment variables to run.
counsel-mcp
MCP server "counsel-mcp", hosted remotely at liki.hk, as configured in ml8s/liki.
linggen
MCP server "linggen", hosted remotely, as configured in linggen/linggen-memory.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
engram-server
MCP server "engram-server" as configured in jamjet-labs/jamjet. Runs in Docker (ghcr.io/jamjet-labs/engram-server:0.5.0).
groundlens
MCP server "groundlens" as configured in groundlens-dev/groundlens. Runs locally from the groundlens[mcp] Python package.