# Bug Bounty Programs (npm · @pipeworx/mcp-bug-bounty-programs)

bug-bounty-programs

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/bug-bounty-programs-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/bug-bounty-programs-mcp)
- npm · `@pipeworx/mcp-bug-bounty-programs`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs.md), [page](https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-bug-bounty-programs`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bug-bounty-programs).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 534 tokens (~178/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Bug Bounty Programs MCP server?

Bug Bounty Programs runs locally as an npm package, launched with npx -y @pipeworx/mcp-bug-bounty-programs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-bug-bounty-programs -- npx -y @pipeworx/mcp-bug-bounty-programs
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-bug-bounty-programs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bug-bounty-programs"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-bug-bounty-programs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bug-bounty-programs"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-bug-bounty-programs -- npx -y @pipeworx/mcp-bug-bounty-programs
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-bug-bounty-programs": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-bug-bounty-programs"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-bug-bounty-programs --command npx --arg -y --arg @pipeworx/mcp-bug-bounty-programs
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-bug-bounty-programs:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-bug-bounty-programs"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-bug-bounty-programs": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-bug-bounty-programs"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-bug-bounty-programs -t stdio -c npx -a -y @pipeworx/mcp-bug-bounty-programs
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-bug-bounty-programs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bug-bounty-programs"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 64, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79)

First indexed and scored.

## MCP tools (3)

### `bounty_programs_search` (~253 tokens)

Search public bug-bounty program directories on Bugcrowd, YesWeHack and HackerOne — program name, cash bounty range, and status (open/paused/disabled), each sourced from that platform's own public, unauthenticated directory. has_wildcard checks real scope asset identifiers on YesWeHack and HackerOne (Bugcrowd's scope is behind a researcher login and is reported as such, not silently empty).

Input parameters:

- `has_wildcard` (boolean): Only programs whose scope includes a wildcard asset ("*.example.com"). Checked via a per-program detail call on yeswehack/hackerone; unavailable for bugcrowd (login-walled).
- `launched_since` (string): ISO date. Only programs with a known launch date on/after this (currently HackerOne only — see bounty_new_programs note).
- `limit` (number): Max rows to return (default 50, max 200).
- `min_bounty` (number): Only programs whose published max bounty (USD) is at least this.
- `platform` (string): Restrict to one platform. Omit to search all three.
- `query` (string): Case-insensitive substring match on the program name.

### `bounty_program` (~123 tokens)

One bug-bounty program by platform + handle: bounty range, status, and scope assets where the platform publishes them without a login. YesWeHack returns a full severity x asset-value reward table; HackerOne returns real scope but no numeric reward table (not exposed publicly); Bugcrowd returns neither (login-walled) and says so.

Input parameters:

- `handle` (string, required): The program's slug/handle on that platform, e.g. "security" on HackerOne or "cryptobox-bug-bounty" on YesWeHack.
- `platform` (string, required)

### `bounty_new_programs` (~99 tokens)

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.

Input parameters:

- `days` (number): Lookback window in days (default 90).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 64
- 2026-10-30: 79

## Common questions

### What is the Bug Bounty Programs MCP server?

Bug Bounty Programs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bug-bounty-programs. bug-bounty-programs. This page covers its npm package (@pipeworx/mcp-bug-bounty-programs).

### Is the Bug Bounty Programs MCP server safe to use?

Bug Bounty Programs scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bug Bounty Programs MCP server expose?

Bug Bounty Programs exposes 3 tools: bounty_programs_search, bounty_program, bounty_new_programs. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.

### Is the Bug Bounty Programs MCP server still maintained?

Bug Bounty Programs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Bug Bounty Programs MCP server under?

Bug Bounty Programs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Bug Bounty Programs MCP server?

VerifyMCP ran 16 checks on Bug Bounty Programs, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-bug-bounty-programs
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-bug-bounty-programs
- Repository: https://github.com/pipeworx-io/mcp-bug-bounty-programs
- Website: https://pipeworx.io/packs/bug-bounty-programs
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-bug-bounty-programs/pipeworx-mcp-bug-bounty-programs