Bounty Operator
io-github-bountyoperator-bounty-operator declares 5 capabilities across 5 tools, with 1 critical issue.
Issues
5 of 5 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
list_profiles | read |
declared |
prepare_review | read |
declared |
build_packet | read |
declared |
account | read |
declared |
run_review | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 13 | tools/list on https://bountyoperator.com/api/mcp, published in the official MCP registry as io.github.bountyoperator/bounty-operator 0.9.18 |
| 2026-10-11 | 13 | tools/list on https://bountyoperator.com/api/mcp, published in the official MCP registry as io.github.bountyoperator/bounty-operator 0.9.12 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.