bounty_new_programs
Pack: bug-bounty-programs · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/bounty_new_programs for the schema, then POST the same URL with its arguments for the data.
Bug-bounty programs launched in the last N days, by real launch date. Currently HackerOne only — the only one of the three platforms that publishes a launched_at field without a login; Bugcrowd and YesWeHack expose no launch-date field at all (confirmed by enumerating their public endpoints), and are named, not silently merged in.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
days | number | no | Lookback window in days (default 90). |
Example call
Arguments
{
"days": 90
}
curl
curl -X POST https://gateway.pipeworx.io/bug-bounty-programs/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"bounty_new_programs","arguments":{"days":90}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('bounty_new_programs', {
"days": 90
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the bug-bounty-programs pack
{
"mcpServers": {
"bug-bounty-programs": {
"url": "https://gateway.pipeworx.io/bug-bounty-programs/mcp"
}
}
}
See Getting Started for client-specific install steps.