BountyVerdict — GitHub & CI Preflight

Choose the right GitHub or CI decision tool for free, then diagnose failed GitHub Actions from a run URL, decide retry versus fix, audit AGENTS.md and…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Choose Github Agent Decision: Call with no arguments for a free six-tool catalog, or choose the economical next call for a GitHub bounty, coding-agent instructions, failed Actions run, retry decision,
  • Check Github Bounty: Is this public GitHub issue bounty still claimable, or is someone already working on it? Checks current status, reward evidence, competing work, and maintainer signals; returns AV
  • Rank Github Bounties: Which public GitHub bounty should I work on next? Compares 2-10 issue URLs, chooses the strongest non-AVOID candidate or recommends none, and returns cited evidence plus partial

What data it sees

Do you need an account

No: the server works without sign-in

Choose the right GitHub or CI decision tool for free, then diagnose failed GitHub Actions from a run URL, decide retry versus fix, audit AGENTS.md and CLAUDE.md, check or rank GitHub bounty issues, and detect breaking MCP tools/list changes. Six paid read-only checks plus a free selector; a first unsigned call returns the exact quote and successful authorized calls cost $0.02-$0.40 USDC via x402 on Base. No buyer API key, repository clone, code execution, or CI mutation.

How to connect

How to connect BountyVerdict — GitHub & CI Preflight to Claude

The server address to paste into Claude settings:

https://bountyverdict--mimirs402.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect BountyVerdict — GitHub & CI Preflight to ChatGPT

The server address to paste into ChatGPT settings:

https://bountyverdict--mimirs402.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect BountyVerdict — GitHub & CI Preflight to Cursor

The server address to paste into Cursor settings:

https://bountyverdict--mimirs402.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (7)

Raw names from tools/list. Only developers need these.

choose_github_agent_decisionCall with no arguments for a free six-tool catalog, or choose the economical next call for a GitHub bounty, coding-agent instructions, failed Actions run, retry decision, or MCP tools change. Returns exact prices, samples, required fields, and unsigned-quote semantics without inspecting the target.
check_github_bountyIs this public GitHub issue bounty still claimable, or is someone already working on it? Checks current status, reward evidence, competing work, and maintainer signals; returns AVOID, CAUTION, or VIABLE. For 2-7 issues, repeated single checks cost less unless one ranked response is worth the premium; use rank_github_bounties for 8-10. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/sample. Exact authorization cap: 0.05 USDC.
rank_github_bountiesWhich public GitHub bounty should I work on next? Compares 2-10 issue URLs, chooses the strongest non-AVOID candidate or recommends none, and returns cited evidence plus partial failures. Its $0.40 price equals eight $0.05 single checks and is cheaper per candidate at 9-10; repeated check_github_bounty calls cost less for 2-7 when ranked orchestration is unnecessary. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/portfolio/sample. Exact authorization cap: 0.40 USDC.
audit_agent_harnessCan a coding agent safely work in this public repository without missing project instructions? Audits AGENTS.md, CLAUDE.md, and related instructions at an immutable commit; does not diagnose CI. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/harness/sample. Exact authorization cap: 0.03 USDC.
diagnose_github_actions_runWhy did this public GitHub Actions run fail, and what should I fix? Uses bounded failed-job logs and redacted evidence. Use classify_github_actions_flake only for retry-once versus fix. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/run/sample. Exact authorization cap: 0.04 USDC.
classify_github_actions_flakeIs this failed GitHub Actions run flaky—should I retry it once or fix the code? Uses the current attempt and bounded history. Use diagnose_github_actions_run for root cause. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/flake/sample. Exact authorization cap: 0.07 USDC.
check_mcp_tool_driftWill upgrading to this complete MCP tools/list break my agent or weaken declared safety hints? Compares caller-supplied baseline and current snapshots; never fetches or invokes tools. Inspect a representative result before paying: https://bountyverdict-agent-production.mimirslab.workers.dev/api/mcp-drift/sample. Exact authorization cap: 0.02 USDC.