Forgejudge MCP server
io.github.ahmedEid1/forgejudge·v0.1.1Open eval leaderboard + CI gate for autonomous coding agents (solve, score, trace).
0 stars
Reviews
Write oneNobody has reviewed Forgejudge yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Forgejudge tools (4, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
_leaderboard_implget_leaderboardReturn the current ForgeJudge leaderboard (one row per model).
get_runwrite actionReturn a single run record (score, patch, Langfuse trace URL) by id.
solve_issuewrite actionRun the ForgeJudge agent on a golden task and grade its patch.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan57 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 36 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Forgejudge compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 1,119 Developer tools servers
- Tools
- 4
- the typical Developer tools server has 7
- Tools that change things
- 50%
- typical: 5%. Fewer write tools means less an agent can break
What its tools let an agent do: 2 read · 2 change
Install Forgejudge in Claude Code, Cursor or VS Code
claude mcp add forgejudge -- uvx forgejudge
What the publisher says
From the Forgejudge repository's README, as published. We do not edit it. Read it on GitHub
ForgeJudge
An open, always-on leaderboard and CI gate for autonomous coding agents — every patch runs in a sandbox, every run has a public trace, every regression fails the build.
▶ Live leaderboard: forgejudge.ahmedhobeishy.tech · playground · methodology · model swap · MCP registry
<!-- mcp-name: io.github.ahmedEid1/forgejudge --> <!-- ^ ownership proof for the MCP registry (validated against this PyPI long-description). -->
Current numbers (hidden-test = the agent never sees the failing test; $0 free tier; same harness, swap the model; 18 tasks × 3 seeds = 54 runs/model, 162 total):
| Model | pass@1 | pass@3 |
|---|---|---|
| gpt-oss-120b | 90.7% | 100% |
| llama-3.3-70b | 88.9% | 94.4% |
| llama-3.1-8b | 48.1% | 66.7% |
The score rises with the better model while the harness stays fixed (model-swap proof), and pass@3 > pass@1 shows real run-to-run variance — which is exactly why the CI gate is multi-seed. Every run deep-links its Langfuse trace.
ForgeJudge is the only open-source autonomous software-engineering agent that proves its quality in public on every commit: a hand-rolled single-agent solver, a deterministic execution-as-judge harness, an always-on leaderboard with per-run traces, and a CI gate that blocks regressions — all on a $0 / self-hostable stack against a contamination-resistant, intrinsically-verifiable golden set.
The engineered harness, observability, and gate are the deliverable — not a high resolution rate. A $0 free-model agent will score modestly by design. We prove value with a model-swap comparison: the score rises with a better model while the harness stays fixed.
How it works
flowchart TD
G["Golden set · Git-canonical<br/>18 intrinsically-verifiable, mutation-hardened<br/>make-CI-green tasks"]
subgraph SOLVER["Single-agent solver"]
direction LR
L["localize<br/>(BM25)"] --> R["repair<br/>(LLM router · critic · syntax edit-gate)"] --> V["validate<br/>(run tests)"]
end
G --> SOLVER
SOLVER --> PATCH["unified diff"]
SOLVER -. "every step traced" .-> TRACE["OTel → Langfuse<br/>per-run public trace"]
PATCH --> H["Deterministic harness, in a sandbox<br/>apply test_patch + candidate patch · run F2P / P2P<br/><b>RESOLVED iff</b> every FAIL_TO_PASS passes AND every PASS_TO_PASS stays green<br/>swebench-equivalent · stricter on skips · cheat-resistant"]
H --> STORE["Run store<br/>Neon + pgvector"]
STORE --> LB["Leaderboard<br/>pass@1 / pass@3 · cost · tokens · trace link"]
H --> GATE["Multi-seed CI gate<br/>a PR that lowers the resolution rate fails the build"]
style G stroke:#3fb950,stroke-width:2px
style H stroke:#4cc2ff,stroke-width:2px
style GATE stroke:#f0883e,stroke-width:2pxShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Forgejudge: common questions
- Is Forgejudge MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Forgejudge safety report
- How do I install Forgejudge?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Forgejudge need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Forgejudge maintained?
- The last commit was 74 days ago (2026-08-22). The latest release is v0.1.1.
- What can I use instead of Forgejudge?
- Servers from other publishers that do the same job: Repowise MCP server, uploads.sh MCP server and Teamcity MCP server.
- How does Forgejudge compare with other Developer tools MCP servers?
- safety score 88/100 (higher than 75% of 1,119 Developer tools servers); tools 4 (the typical Developer tools server has 7); tools that change things 50% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Forgejudge
Same job from other publishers: the closest match first, then the best rated.
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB
uploads.shHost files from coding agents; stage on a branch and attach to GitHub PRs.not reviewedEstablishedA- TeamcityMCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistantsnot reviewedEstablishedB
- ForemergeCoordinate parallel coding agents, above Gitnot reviewedGrowingA
- RepoPilotLocal, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.not reviewedGrowingA