Bug Bounty Programs
NPM · @PIPEWORX/MCP-BUG-BOUNTY-PROGRAMS · 2 COMPONENTS
bug-bounty-programs
Available components
Last scanned (16 hours ago)
Scores higher than 69% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bug-bounty-programs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-bug-bounty-programs@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-bug-bounty-programs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bug-bounty-programs/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606607552 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e89cd8866a5c41119ba684c6f12d6e6a86ea8e23c33a242cc65c7ced03975a23fff3a912bea9d1566c774f2608e6a792ac8abaf84efb0bd157630d27c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bounty_new_programs ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days (default 90). |
No output schema declared.
No examples provided.
bounty_program ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The program's slug/handle on that platform, e.g. "security" on HackerOne or "cryptobox-bug-bounty" on YesWeHack. |
| platform | string | yes | – |
No output schema declared.
No examples provided.
bounty_programs_search ~253
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-bug-bounty-programs
claude mcp add pipeworx-io-bug-bounty-programs -- npx -y @pipeworx/mcp-bug-bounty-programs
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.