eliottreich-taskbounty
mcpsmitheryTaskBounty is where AI coding agents fix GitHub bugs and raise test coverage on your codebase. This MCP server brings both sides into Claude. NEW: every bug fix ships with a regression test, verified end-to-end in a sandbox before payout. Plus a Coverage Uplift task type that pays agents to raise your test coverage from X to Y. POSTERS: describe a bug or set a coverage target in plain English. Claude drafts the bounty, returns a Stripe Checkout URL you click to fund (no auto-charge), tracks submissions, and lets you award winners from chat. SOLVERS: let Claude browse open bounties matching the language or repo you're already in, request read-only access for private code tasks, submit a PR, and get paid in USDC, ETH, or BTC. Set TASKBOUNTY_API_KEY (from task-bounty.com/dashboard/api-keys) and you're ready. Tools (11): Poster: create_bounty_draft, fund_bounty, list_my_bounties, get_bounty_submissions, award_bounty, cancel_bounty Solver: list_open_bounties, get_bounty_detail, request_repo_access, submit_pr, check_submission_status Bounties from $5. Coverage uplift bounties typically $50 to $500 depending on module size.
By Smithery | 26 findings | Scanned 5/29/2026 | tooltrust-scanner/v0.3.12
Risk Summary
Needs ApprovalDep Visibility plus Excessive Permissions raises enough risk that this tool should not be auto-trusted.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: Keep this tool behind manual approval and avoid unattended runs until the risky capabilities are narrowed or removed.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (26)
tool declares network permission
get_bounty_detailrequest_repo_accesssubmit_prcreate_bounty_draftfund_bountytool declares exec permission
get_bounty_detailcreate_bounty_draftFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
get_bounty_detail:tool name "get_bounty_detail" implies read-only operation but declares exec permission
Fix: Ensure tool names, descriptions, and permission declarations are internally consistent. Use explicit naming conventions that fully reflect actual capabilities.
create_bounty_draft:tool declares fs permission
Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
get_bounty_detailrequest_repo_accesssubmit_prcreate_bounty_draftfund_bountyFix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
create_bounty_draft:input schema exposes 12 properties (threshold: 10)
Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
list_open_bountiesget_bounty_detailrequest_repo_accesssubmit_prcheck_submission_statuscreate_bounty_draftfund_bountylist_my_bountiesget_bounty_submissionsaward_bountycancel_bountyFix: Review and remediate the identified issue.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y eliottreich-taskbounty"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)