Claude Code Bug Bounty Programs archive_evidence
How to: Claude Code Bug Bounty Programs archive_evidence
Add Bug Bounty Programs to Claude Code
-
01
Run this in your project directory.
claude mcp add --transport http bug-bounty-programs https://gateway.pipeworx.io/bug-bounty-programs/mcp-
02
Restart your session so the server is picked up.
-
03
Ask for something archive_evidence does. Claude Code lists the server's tools on connect and calls archive_evidence itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Bug Bounty Programs's identifier in your config matches the one above exactly.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Set these first
Bug Bounty Programs will not start until these are set, so archive_evidence never becomes available.
-
PIPEWORX_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.