Skip to content
Agentmart
Submit a tool

Judges Panel

45 judges that evaluate AI-generated code for security, cost, and quality with built-in AST.

Connector by KevinRabun · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 7
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/kevinrabun-judges

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

45 judges that evaluate AI-generated code for security, cost, and quality with built-in AST.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
25 read · 3 write · 0 delete · 7 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 35

Read from the source code; the running server may list different tools.

Read 25 · Look things up without changing anything.

  • analyze_dependencies
  • evaluate_batch
  • evaluate_code
  • evaluate_code_single_judge
  • evaluate_code_streaming
  • evaluate_diff
  • evaluate_file
  • evaluate_git_diff
  • evaluate_project
  • evaluate_then_fix
  • evaluate_with_progress
  • evaluate-code
Show 13 more tools
  • evaluate-diff
  • explain_finding
  • fix_code
  • get_finding_stats
  • get_judges
  • get_suppression_analytics
  • judges_evaluate
  • list_files
  • list_triaged_findings
  • re_evaluate_with_context
  • read_file
  • review-project
  • session_status

Write 3 · Create, change, send or run things.

  • benchmark_gate
  • record_feedback
  • run_benchmark

Not yet classified 7 · We could not tell from the name and description.

  • evaluate_app_builder_flow
  • evaluate_focused
  • evaluate_policy_aware
  • evaluate_public_repo_report
  • scaffold_judge
  • scaffold_plugin
  • triage_finding

Files it touches

  • Any path the agent passes to its tools

Tools (35)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • analyze_dependencies

    Analyze a PACKAGE MANAGER manifest file (NOT infrastructure code) for supply-chain risks, version pinning issues, typosquatting indicators, and dependency hygiene. ONLY accepts: package.json, requirements.txt, Cargo.toml, go.mod, pom.xml, .csproj. Do NOT use this for Bicep, Terraform, ARM templates, CloudFormation, Dockerfiles, or any other infrastructure/deployment configuration — use evaluate_code or evaluate_code_single_judge for those.

  • benchmark_gate

    Run the benchmark suite and check results against quality thresholds. Returns pass/fail with metric details including F1, precision, recall, and detection rate. Use in CI pipelines to prevent quality regressions.

  • evaluate_app_builder_flow

    Run a 3-step app-builder workflow: tribunal review, plain-language risk translation, and prioritized remediation tasks with AI-fixable P0/P1 items.

  • evaluate_batch

    Evaluate multiple code files in a single call. Returns per-file verdicts with scores and findings, plus aggregate statistics.

  • evaluate_code

    Description is built at runtime.

  • evaluate_code_single_judge

    Description is built at runtime.

  • evaluate_code_streaming

    Description is built at runtime.

  • evaluate_diff

    Description is built at runtime.

  • evaluate_file

    Description is built at runtime.

  • evaluate_focused

    Run a focused evaluation using only the specified judges. Use this after an initial full evaluation to re-check specific areas — for example, re-run only 'cybersecurity' and 'authentication' judges after applying security fixes. Much faster than a full tribunal evaluation.

  • evaluate_git_diff

    Evaluate code changes from a git diff. Parses the unified diff from a git repository, identifies changed files and lines, and runs the full tribunal on each changed file — filtering findings to only those on changed lines. Supports both live git repos (provide repoPath + base ref) and pre-computed diffs (provide diffText).

  • evaluate_policy_aware

    Run policy-aware tribunal evaluation with named policy profiles (startup, regulated, healthcare, fintech, public-sector), evidence calibration from runtime metrics, specialty-per-judge feedback, confidence scoring, and uncertainty reporting. Use this when code must meet specific compliance or vertical requirements.

  • evaluate_project

    Description is built at runtime.

  • evaluate_public_repo_report

    Clone a public repository URL, run the full judges panel across source files, and generate a consolidated markdown report.

  • evaluate_then_fix

    Evaluate code and automatically generate fix patches for all findings that have auto-fix support. Returns the evaluation verdict alongside ready-to-apply patches. Use this for a single-step 'review + fix' workflow.

Show 20 more tools
  • evaluate_with_progress

    Evaluate code with progressive judge-by-judge reporting. Returns intermediate counts as each judge completes, useful for large files where full tribunal takes time.

  • evaluate-code

    Evaluate a code snippet or file for issues across all judge categories

  • evaluate-diff

    Evaluate a code diff (PR or commit) for introduced issues

  • explain_finding

    Explain a Judges Panel finding in plain language. Provides OWASP/CWE references, risk context, and remediation guidance based on the rule ID and finding details.

  • fix_code

    Evaluate code with the Judges Panel and automatically apply all available auto-fix patches. Returns the fixed code along with a summary of applied and remaining findings. Use this to fix security, performance, and quality issues in a single step.

  • get_finding_stats

    Get finding lifecycle statistics for the project: open, fixed, recurring, and triaged finding counts plus trends. Shows whether code quality is improving or declining over evaluation runs.

  • get_judges

    List all available judges on the Agent Tribunal panel, including their areas of expertise and what they evaluate.

  • get_suppression_analytics

    Analyze finding suppression patterns: FP rates by rule, suppression rates by judge, auto-suppress candidates, and actionable recommendations for tuning. Use this to understand which rules need calibration.

  • judges_evaluate
  • list_files

    List files and directories in the workspace. Useful for exploring project structure before evaluating code.

  • list_triaged_findings

    List findings that have been triaged (accepted-risk, deferred, wont-fix, false-positive). Optionally filter by triage status. Shows the triage decision, reason, and who made it.

  • re_evaluate_with_context

    Re-evaluate code with developer-provided context from a multi-turn conversation. Accepts disputed findings, accepted findings, and additional context to adjust the evaluation. This is the agentic feedback loop — the developer explains their intent and the tribunal re-evaluates with that context, applying auto-tune and confidence filtering.

  • read_file

    Read the contents of a file in the workspace. Returns the file text, or an error if the file is too large or missing.

  • record_feedback

    Record user feedback on a finding — mark it as a true positive (tp), false positive (fp), or won't fix (wontfix). This feedback calibrates confidence scores in subsequent evaluations during the current session, reducing noise from rules the user considers inaccurate.

  • review-project

    Full project-level review with cross-file analysis

  • run_benchmark

    Run the full benchmark suite and return a detailed dashboard with per-judge, per-category, and per-difficulty breakdowns. Includes precision, recall, F1, false positive rates, and individual case results. Use this to understand overall system quality and identify weak spots.

  • scaffold_judge

    Generate the boilerplate files to add a new judge to the Judges Panel. Creates the judge definition (with self-registration), evaluator skeleton, and tells you the one line to add to index.ts. Validates that the judge ID and rule prefix are unique.

  • scaffold_plugin

    Generate a starter plugin template for the Judges Panel. Creates a self-contained plugin file with custom rules, optional custom judges, and lifecycle hooks.

  • session_status

    Get the current evaluation session status — how many evaluations have been run, detected frameworks, verdict history per file, and stability indicators. Useful for understanding what the tribunal has already reviewed.

  • triage_finding

    Set the triage status of a tracked finding. Records the decision (accepted-risk, deferred, wont-fix, false-positive) with attribution and reason. Feeds back into calibration to reduce future false positives.

Signals

Stars
7
Forks
4
Open issues
3
Weekly downloads
39
Last commit
Apr 7, 2026 (6 months ago)
Last release
Apr 7, 2026 (6 months ago)
Last package publish
Apr 7, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.KevinRabun/judges
Version
3.129.9
Auth
No auth
Packages
npm @kevinrabun/judges
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from KevinRabun

Cite this page

Judges Panel MCP server. Agent Mart. https://agentmart.dev/connectors/kevinrabun-judges (last updated 2026-10-24)