BugSecure MCP
Related Servers
Alternatives to BugSecure MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceLets AI assistants browse bug bounty programmes, work on vulnerability reports, and help with triage while acting under user-approved permissions.-
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with HackerOne for managing reports, checking program scope, analyzing earnings, and more through natural language commands.28-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Intigriti by syncing programs, scopes, and rules of engagement, then provides tools to search and generate actionable attack briefings.2MIT
- AlicenseAqualityBmaintenanceEnables AI assistants and agents to search bug bounty programs, retrieve policies and scopes, and check targets against active scope across HackerOne, YesWeHack, and Intigriti using personal API credentials.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to query bug-bounty programs, scopes, rules, payouts, reports, statistics, and researcher rankings through the platform's public API, with optional private-program access via a session cookie.101MIT
- AlicenseCqualityDmaintenanceEnables AI agents to generate and manage specialized bug bounty hunting workflows including reconnaissance, vulnerability testing, OSINT gathering, and file upload testing. Provides REST API endpoints for comprehensive security assessments with intelligence-driven vulnerability prioritization.402MIT
TDQS
Scored across 33 tools
The surface cleanly separates researcher-side and organisation-side actions, with descriptions that cross-reference paired tools. However, several near-name pairs such as get_report/get_org_report, list_my_reports/list_org_reports, search/search_programs, and get_org_report_stats/get_program_stats require careful reading to avoid choosing the wrong side.
All tools use snake_case with a consistent verb-first pattern: get_, list_, add_, update_, search_, check_, assign_, grade_, mark_, raise_, save_, submit_, and verify_. The my_/org_ prefixes are used consistently to distinguish the user's resources from organisation resources.
At 33 tools, this set is well beyond the typical 3–15 range and exceeds the 25+ heavy threshold. The two-sided platform explains some breadth, but many narrowly scoped tools create a significant selection burden and could likely be consolidated.
Coverage spans researcher reporting, organisation triage and grading, appeals, payout certificates, notifications, disclosures, profiles, programmes, and taxonomy. Operations intentionally kept on the BugSecure website are explicitly identified, leaving no obvious lifecycle dead ends for MCP-appropriate actions.