A
license-
qualityF
maintenanceProvides paid decision APIs for autonomous coding agents to diagnose GitHub Actions failures, classify flaky tests, check MCP tool drift, audit agent instructions, and compare bounties.
MIT
BountyVerdict Agent Decision Tools
Server Details
Free selector plus read-only GitHub bounty, agent harness, Actions, flake, and MCP drift decisions.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Mimirs402/bountyverdict
- GitHub Stars
- 1
- Server Listing
- BountyVerdict
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.4/5 across 7 of 7 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a distinct purpose: auditing repo instructions, checking bounties, comparing MCP snapshots, routing decisions, classifying flakes, diagnosing failures, and ranking bounties. Overlapping pairs (bounty check/rank, flake/diagnose) are explicitly cross-referenced with usage guidance, so agents can reliably select the correct tool.
Naming Consistency5/5
All tool names follow a consistent verb_noun (snake_case) pattern: audit, check, check, choose, classify, diagnose, rank. The repeated 'check' is acceptable as the verbs are otherwise distinct, and the nouns clearly indicate the target domain. The naming is predictable and readable.
Tool Count5/5
With 7 tools, the set is well-scoped and each tool addresses a specific decision point. The count is within the ideal range for a focused decision-support server, and no tool feels redundant or unnecessary; the meta-tool (choose_github_agent_decision) adds value by optimizing call selection.
Completeness5/5
The tools cover the full decision space implied by the server's purpose: bounties (single check and batch ranking), CI failures (flake classification and root-cause diagnosis), MCP drift detection, and repository instruction auditing. The router tool ties them together, and no obvious missing operation (e.g., update or act) is required for a decision-only server.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityAmaintenanceCI health reports for GitHub Actions: flaky tests named from logs, wasted compute priced in dollars, zombie crons, PR feedback time, plus 21 lint rules with safe auto-fixes. Read-only MCP tools wrap the same Go binary.MIT
- AlicenseCqualityBmaintenanceA policy-aware MCP server for GitHub and GitHub Actions that enables safe AI-assisted infrastructure workflows—inspecting repositories, preparing branches and pull requests, and constrained remote mutations behind explicit preview-bound approval tokens.18MIT
- Alicense-qualityBmaintenanceEnables autonomous triage of GitHub issues and pull requests through MCP, with classification, deduplication, prioritization, and safe human-in-the-loop actions.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.