Bug Bounty Programs MCP server

@pipeworx/bug-bounty-programs

Public bug-bounty PROGRAM DIRECTORY data — program name, bounty range, status and scope assets — from Bugcrowd, YesWeHack and HackerOne's own public directories. No vulnerability content, no researcher profiles or handles.

Part of Pipeworx — an MCP gateway connecting AI agents to 1743+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• bountyprogramssearch(platform?, query?, minbounty?, launchedsince?, haswildcard?, limit?) — search across one or all three platforms by name, minimum bounty (USD), launch date (HackerOne only — see below), and whether scope includes a wildcard asset like .example.com (checked live on yeswehack/hackerone; bugcrowd returns a count: 0 with an explanatory note instead of an error, because its scope is login-walled, not broken).
• bounty_program(platform, handle) — one program by platform + handle. YesWeHack returns a full severity x asset-value reward table and real scope; HackerOne returns real scope but no numeric reward table (not exposed anywhere on the public schema); Bugcrowd returns neither and says why.
• bountynewprograms(days) — programs launched in the last N days, by real launch date. HackerOne only; see "What's not here" below for why Bugcrowd/YesWeHack can't contribute to this one honestly.

Auth

Keyless. Every endpoint below answers with no account, token, or API key.

Data sources

• https://bugcrowd.com/engagements.json — paged (?page=N, 24/page, paginationMeta.totalCount) public program list: name, URL, reward summary, industry, access status. No scope/target data — Bugcrowd's scope "reveal" action redirects to /h/engagements/{handle}/reveal.json, its researcher-sign-in area. That is a genuine login wall, not a bug, and bountyprogram/haswildcard say so rather than returning a silent empty result.
• https://api.yeswehack.com/programs (list, ?page=N) and https://api.yeswehack.com/programs/{slug} (detail) — the richest of the three. Detail returns scopes[] (real asset identifiers, some with wildcards), outofscope, and rewardgriddefault/low/medium/high/critical/verylow — a real severity x asset-value-tier reward table (only the tiers the program actually uses have non-null values; everything else is null, not zero). No launch-date field anywhere on this endpoint — only lastupdateat (last change, never surfaced as launchedat here to avoid implying a launch).
• https://hackerone.com/graphql (POST, unauthenticated) — query { teams } / query { team(handle) }. Introspection is disabled, so every field name below was found by probing a guess and reading GraphQL's own "did you mean X?" error back, not from a published schema doc:
• teams(first/last, after/before): handle name offersbounties submissionstate launchedat — launchedat is a REAL, verified launch date (confirmed against hackerone.com/security → 2013-11-06, the platform's own founding program). last: N returns the N most-recently-created teams, which is what bountynewprograms walks backward from; there is no working orderby value we could find (orderby: {field: ..., direction: DESC} is accepted syntactically but every field name we tried for field was rejected), so sorting relies on sequential internal IDs rather than an explicit date sort.
• team(handle).structuredscopessearch(first): a union (DocumentUnion) — use ... on StructuredScopeDocument { identifier assettype eligibleforbounty eligibleforsubmission instruction }. identifier is the actual scope asset (domain/URL), sometimes a wildcard (.rubyonrails.org, .cloudflarepartners.com confirmed live). No numeric bounty amount anywhere we could find — team.bountytable exists as a type but every plausible field name on it (rewards, severities, lowbounty/highbounty, min/max,

Shortened. The full README is on GitHub.