BountyVerdict Agent Decision Tools
REMOTE · BOUNTYVERDICT-AGENT-PRODUCTION.MIMIRSLAB.WORKERS.DEV
Read-only GitHub bounty, agent harness, Actions failure, flake, and MCP tool-drift decisions.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Aug 26 0
- Server version: 1.1.22 → 1.1.25 functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bountyverdict-agent-production.mimirslab.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mimirslab.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 50132fa43d1d455eef4393b528281d02195 |
| SANs: *.mimirslab.workers.dev, mimirslab.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bountyverdict-agent-production.mimirslab.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bountyverdict-agent-production.mimirslab.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://bountyverdict-agent-production.mimirslab.workers.dev/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_agent_harness Audit coding-agent repository instructions ~129
Can 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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_url | string | yes | Canonical public GitHub repository URL, for example https://github.com/owner/repository. No subpath, query string, fragment, or non-GitHub host. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| findings | array | yes | – |
| product | string | yes | – |
| recommendations | array | yes | – |
| repository | object | yes | – |
| score | integer | yes | – |
| service_reuse | object | yes | – |
| summary | string | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
check_github_bounty Check GitHub bounty claimability risk ~171
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_url | string | yes | Canonical public GitHub issue URL, for example https://github.com/owner/repository/issues/123. No query string, fragment, pull request, or non-GitHub host. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| issue | object | yes | – |
| linked_source | object | yes | – |
| product | string | yes | – |
| score | integer | yes | – |
| service_reuse | object | yes | – |
| signals | array | yes | – |
| summary | string | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
check_mcp_tool_drift Check whether an MCP tools update is breaking ~169
Will 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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_source_trust | string | yes | Whether the caller recognizes the annotation source. Annotations never become runtime-behavior proof. |
| baseline | object | yes | Complete previously accepted tools/list snapshot. |
| contract_version | string | yes | – |
| current | object | yes | Complete candidate tools/list snapshot. |
| subject | object | yes | Caller-chosen identity for the MCP server being compared; ownership is not verified. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| contract_version | string | yes | – |
| findings | array | yes | – |
| hashes | object | yes | – |
| ruleset_version | string | yes | – |
| service | string | yes | – |
| service_reuse | string | yes | – |
| summary | object | yes | – |
| trust | object | yes | – |
| verdict | string | yes | – |
No examples provided.
choose_github_agent_decision Choose the right GitHub agent decision tool for free ~221
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, or MCP tools change. Returns exact prices, samples, required fields, and unsigned-quote semantics without inspecting the target.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_count | integer | – | Required only for bounty_portfolio: exact number of distinct issue URLs. |
| needs_ranked_response | boolean | – | For bounty_portfolio only. True when one ranked, partial-failure-aware response is worth the premium; otherwise 2-7 route to cheaper repeated single checks. |
| task | string | – | Optional exact task. Omit all arguments for the six-tool catalog. one_bounty = claimability of one issue; bounty_portfolio = economical handling of 2-10 issues; repository_agent_instructions = pre-co… |
| Name | Type | Req | Description |
|---|---|---|---|
| decision_returned | array | – | – |
| free_sample | string | – | – |
| next_action | string | – | – |
| next_call | object | – | – |
| not_for | string | – | – |
| product | string | – | – |
| selector_call_payment_required | boolean | yes | – |
| task | string | – | – |
| tools | array | – | – |
| total_price_usdc | string | – | – |
| unsigned_quote_cannot_charge | boolean | – | – |
| use_when | string | – | – |
No examples provided.
classify_github_actions_flake Decide whether to retry failed GitHub Actions ~167
Is 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.
| Name | Type | Req | Description |
|---|---|---|---|
| attempt | integer | – | Optional exact workflow run attempt number, starting at 1. Omit to use the run URL's latest available completed attempt. |
| run_url | string | yes | Canonical public GitHub Actions run URL, for example https://github.com/owner/repository/actions/runs/123456. No job URL, query string, fragment, or non-GitHub host. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| decision | object | yes | – |
| failure_signatures | array | yes | – |
| product | string | yes | – |
| service_reuse | object | yes | – |
| summary | string | yes | – |
| target | object | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
diagnose_github_actions_run Find why a GitHub Actions run failed ~138
Why 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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_url | string | yes | Canonical public GitHub Actions run URL, for example https://github.com/owner/repository/actions/runs/123456. No job URL, query string, fragment, or non-GitHub host. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| diagnosis | object | yes | – |
| next_actions | array | yes | – |
| product | string | yes | – |
| retryability | string | yes | – |
| run | object | yes | – |
| service_reuse | object | yes | – |
| summary | string | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
rank_github_bounties Choose the best GitHub bounty ~162
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_urls | array | yes | Two to ten distinct canonical public GitHub issue URLs. Duplicate issue URLs are rejected before payment. |
| Name | Type | Req | Description |
|---|---|---|---|
| best_candidate | – | yes | – |
| checked_at | string | yes | – |
| counts | object | yes | – |
| failures | array | yes | – |
| product | string | yes | – |
| ranked | array | yes | – |
| recommendation | string | yes | – |
| service_reuse | object | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the BountyVerdict Agent Decision Tools MCP server?
BountyVerdict Agent Decision Tools is a hosted endpoint at https://bountyverdict-agent-production.mimirslab.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bountyverdict-agent-production.mimirslab.workers.dev
claude mcp add --transport http cristianmoroaica-bountyverdict 'https://bountyverdict-agent-production.mimirslab.workers.dev/mcp'
What is the BountyVerdict Agent Decision Tools MCP server?
BountyVerdict Agent Decision Tools is an MCP server listed in the public MCP registry as io.github.cristianmoroaica/bountyverdict. Read-only GitHub bounty, agent harness, Actions failure, flake, and MCP tool-drift decisions. This page covers its hosted endpoint (https://bountyverdict-agent-production.mimirslab.workers.dev/mcp).
Is the BountyVerdict Agent Decision Tools MCP server safe to use?
BountyVerdict Agent Decision Tools scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BountyVerdict Agent Decision Tools MCP server expose?
BountyVerdict Agent Decision Tools exposes 7 tools: choose_github_agent_decision, check_github_bounty, rank_github_bounties, audit_agent_harness, diagnose_github_actions_run, and 2 more. Their descriptions and schemas cost roughly 1,157 tokens of context every time the server is loaded.
Does the BountyVerdict Agent Decision Tools MCP server require authentication?
Its publisher declares no required credentials for BountyVerdict Agent Decision Tools. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BountyVerdict Agent Decision Tools MCP server still maintained?
BountyVerdict Agent Decision Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.