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/weather)<a href="https://agentmods.dev/mcp/joshrotenberg/tower-mcp/weather"><img src="https://agentmods.dev/badge/mcp/joshrotenberg/tower-mcp/weather.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
weather 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 8d 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
{
"weather": {
"command": "cargo",
"args": [
"run",
"-p",
"tower-mcp-examples",
"--example",
"weather_server"
],
"env": {
"RUST_LOG": "tower_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.
- 8d ago First seen · 15 lines scan A 69436b2142c3
weather is an MCP server published in the GitHub repository joshrotenberg/tower-mcp (10 stars, last pushed 4d ago), 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
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
anodizer
MCP server "anodizer" as configured in tj-smith47/anodizer. Runs in Docker (ghcr.io/tj-smith47/anodizer).
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
protocol-conformance
MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib. Runs locally from the mcp-protocol-conformance npm package.
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.
vastlint
MCP server "vastlint" as configured in aleksUIX/vastlint. Launched with https://github.com/aleksUIX/vastlint/releases/download/v0.9.1/vastlint-mcp-linux.