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/ahmedEid1/forgejudgeWrote 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/ahmedeid1/forgejudge/mcp-forgejudge)<a href="https://agentmods.dev/mcp/ahmedeid1/forgejudge/mcp-forgejudge"><img src="https://agentmods.dev/badge/mcp/ahmedeid1/forgejudge/mcp-forgejudge/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/ahmedeid1/forgejudge/mcp-forgejudge"><img src="https://agentmods.dev/badge/mcp/ahmedeid1/forgejudge/mcp-forgejudge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
forgejudge 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 11d 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
{
"forgejudge": {
"command": "uvx",
"args": [
"forgejudge",
"forgejudge[mcp]==0.1.0",
"python",
"-m",
"forgejudge.mcp.server"
],
"env": {}
}
}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.
- 11d ago First seen · 13 lines scan A 69f853fd7ad1
forgejudge is an MCP server published in the GitHub repository ahmedEid1/forgejudge (0 stars, last pushed 21d 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
playwright
MCP server "playwright" as configured in langwatch/langwatch. Launched with bash -c d=$PWD; while [ "$d" != / ] && [ ! -f "$d/dev/scripts/playwright-mcp.sh".
codebase-memory-mcp
MCP server "codebase-memory-mcp" as configured in suyoumo/ClawProBench. Launched with codebase-memory-mcp.
CodSpeed
MCP server "CodSpeed", hosted remotely at mcp.codspeed.io, as configured in CodSpeedHQ/codspeed.
evalview
MCP server "evalview" as configured in hidai25/eval-view. Launched with evalview mcp serve. Needs 2 environment variables to run.
evalview-mcp
Open-source testing and regression detection framework for AI agents. Golden baseline diffing, CI/CD integration, works with LangGraph, CrewAI, OpenAI, Anthropic Claude, HuggingFace, Ollama, and MCP. Runs locally from the evalview Python package. Needs 1 environment variable to run.
opengate-mcp
Check whether an AI answer is grounded in its context — deterministic, no LLM judge. Runs locally from the @pharmatools/opengate-mcp npm package.