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/Forward-Future/DeployBotWrote 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/forward-future/deploybot/claude-code-deploybot)<a href="https://agentmods.dev/mcp/forward-future/deploybot/claude-code-deploybot"><img src="https://agentmods.dev/badge/mcp/forward-future/deploybot/claude-code-deploybot/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/forward-future/deploybot/claude-code-deploybot"><img src="https://agentmods.dev/badge/mcp/forward-future/deploybot/claude-code-deploybot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deploybot 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
{
"deploybot": {
"command": "uvx",
"args": [
"--from",
"deploybot-merge-queue[mcp] @ git+https://github.com/Forward-Future/DeployBot.git@3fb42e2e3cf3a6f21cddf43e3d06deaa24a3ac80",
"deploybot-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.
- 1mo ago First seen · 10 lines scan A c9e076bffe89
deploybot is an MCP server published in the GitHub repository Forward-Future/DeployBot (44 stars, last pushed 3mo 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
tapp
Autonomous QA for iOS + web — agents get a deterministic ship/no-ship verdict, no test code. Runs locally from the tapp-mcp npm package.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.
doc-bridge
Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code. Runs locally from the @agentskit/doc-bridge npm package.
gha-doctor
MCP server "gha-doctor" as configured in linnea-bakshi/gha-doctor. Runs in Docker (ghcr.io/linnea-bakshi/gha-doctor:0.66.0). Needs 1 environment variable to run.
branchlift
Stateful backend environments for parallel coding agents and git worktrees. Runs locally from the branchlift npm package.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.