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/jbr/ferritinWrote 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/jbr/ferritin/rustdoc)<a href="https://agentmods.dev/mcp/jbr/ferritin/rustdoc"><img src="https://agentmods.dev/badge/mcp/jbr/ferritin/rustdoc/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/jbr/ferritin/rustdoc"><img src="https://agentmods.dev/badge/mcp/jbr/ferritin/rustdoc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rustdoc 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
{ "rustdoc": { "url": "https://ferritin.rs/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 b2bc57f0fa5f
rustdoc is an MCP server published in the GitHub repository jbr/ferritin (38 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-30.
Other mcp servers, from other repositories
rust-crate-docs-docker
MCP server "rust-crate-docs-docker" as configured in elasticdotventures/b00t. Runs in Docker (ghcr.io/promptexecution/rust-cargo-docs-rag-mcp:latest).
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.
cpp-lectures-mcp
MCP server "cpp-lectures-mcp" as configured in Alexvozhak/cpp-lectures-mcp. Runs locally from the cpp-lectures-mcp Python package.
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.
bls-mcp
MCP server "bls-mcp", hosted remotely at 127.0.0.1, as configured in openai/openai-cookbook.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const d=process.cwd();const S=n=>{const…