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/vigilancetrent/mcpforgeWrote 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/vigilancetrent/mcpforge/mcpforge)<a href="https://agentmods.dev/mcp/vigilancetrent/mcpforge/mcpforge"><img src="https://agentmods.dev/badge/mcp/vigilancetrent/mcpforge/mcpforge/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/vigilancetrent/mcpforge/mcpforge"><img src="https://agentmods.dev/badge/mcp/vigilancetrent/mcpforge/mcpforge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcpforge 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 2mo 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
{ "mcpforge": { "command": "uvx", "args": [ "mcpforge" ] } }
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.
- 2mo ago First seen · 8 lines scan A 9e6b46753bf6
mcpforge is an MCP server published in the GitHub repository vigilancetrent/mcpforge (0 stars, last pushed 6mo 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-31.
Other mcp servers, from other repositories
qobrix-crm-mcp
MCP server "qobrix-crm-mcp" as configured in gca-ltd/qobrix-crm-mcp. Runs locally from the qobrix-crm-mcp npm package.
github
MCP server "github" as configured in Bike4Mind/bike4mind. Runs in Docker (ghcr.io/github/github-mcp-server).
tierline
MCP server "tierline" as configured in jayj221/tierline. Runs locally from the tierline npm package.
mcp
Build, version, review, and export websites, web apps, and games from a conversation. Remote server at 2ools.app.
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.
codereview-mcp
MCP server "codereview-mcp" as configured in lfylow/codereview-mcp. Runs locally from the codereview-mcp Python package.