Bounty Operator MCP server

The remote endpoint exposes five tools. Three run with no account, so an agent can prepare a review and package the result on the first call. The local server adds a sixth, run_gauntlet_plan, and reads files by path.

Code security review, Solidity review and Challenge a draft report are the three core profiles. prepare_review hands their request to your agent’s own model. Every other profile runs on the hosted service through run_review, and so do seven of the gauntlet’s stages.

A call takes up to 50 text files, 120 KB per file, 240 KB and 20,000 lines in total. File names are repo-relative paths such as src/Vault.sol. When the privacy check blocks a file, the result lists the file, the line and the kind of match, and never the matched text.

The remote endpoint takes file text inline as files. On the local server, prepare_review and run_review also take paths: the server reads those files under its working directory, so your agent does not send the text. A client that starts the server outside your project sets BOUNTY_OPERATOR_ROOT to the project folder.

A first request to try:

Use bounty-operator to prepare a Solidity review of src/Vault.sol. Answer the request it returns, then build the packet.

list_profiles marks every profile. hosted: false is one of the three core profiles: its method is open source and prepare_review hands it to your agent. hosted: true is a hosted profile: the service adds its method when run_review runs and sends it with your files to the provider you named, under your key. It is not in the local package or in the public repository, and no tool or prompt returns it.

For a hosted profile the tools answer like this:

The refusal, as the remote endpoint returns it for triage:

{
  "profile": "triage",
  "error": "Triager simulation runs on the server. Call run_review with profile \"triage\", your connection token and your provider key in the X-Provider-Key header.",
  "code": "hosted_profile"
}

The local server returns the same code and names BOUNTY_OPERATOR_TOKEN in the sentence. run_review sends the files and your provider key to the service, which adds the method of the profile, calls your provider and returns the review.

The server ships three prompts. A client that supports MCP prompts lists them as commands. In Claude Code, type / and pick one, or type the full name:

challenge-report and solidity-review prepare the review with prepare_review, have your agent’s own model answer and end with build_packet, so both work with no account.

gauntlet lists the eight stages with the tool that runs each one. Seven are hosted and run through run_review. The report stage is a core profile, so your agent’s own model answers it from prepare_review. The run needs an account token and your provider key, and it uses seven hosted reviews. Free covers one hosted review per UTC day, so a full run takes Operator. On the local server the prompt starts from run_gauntlet_plan.

The repository is also a Claude Code plugin with five skills. challenge-report, solidity-review and code-security-review carry the three core methods and run on your agent’s own model with no account. gauntlet runs the eight stages through this server. hunt-with-gate runs only when you call it by name: it checks a finding before any report is written and never submits anything.

claude plugin marketplace add bountyoperator/bounty-operator
claude plugin install bounty-operator@bounty-operator

The plugin adds this server too. It reads BOUNTY_OPERATOR_TOKEN and BOUNTY_OPERATOR_PROVIDER_KEY from the environment you start Claude Code in; both can stay unset for the core skills. Codex, Cursor and other agents take the skills with one command and the server with the commands above:

npx skills add bountyoperator/bounty-operator

Create a token

1. Sign in at bountyoperator.com with your passkey and open the account panel.
2. Under Connections, name the connection after the client that will use it, and create it.
3. Copy the token. It starts with bok_ and is shown once.
4. Set it as BOUNTY_OPERATOR_TOKEN in your environment and add the server with the token command for your client.

A token lasts 90 days. An account holds three at a time. Revoke one in the account panel and it stops working at once.

Your provider key

run_review runs on your own model key. The remote endpoint takes it in the X-Provider-Key header. The local server reads it from the provider’s environment variable:

The remote endpoint uses the provider’s default model when a call names none. The local server needs a model: pass model, or set BOUNTY_OPERATOR_MODEL.

A failed tool call comes back as a result with isError set and one JSON object: error, a sentence your agent can act on, and code, a value that does not change. Both servers use the same codes.

account and run_review without a valid token are answered with HTTP 401 by the remote endpoint, which is what makes a client ask for the token. The local server returns the code token.