BugSecure MCP
Related Servers
Alternatives to BugSecure MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables authorized bug bounty automation via a scope-enforced MCP bridge, supporting web, secrets, mobile, and LLM red-team scanning, with reporting and advisory.MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated bug bounty hunting and security research with tools for reconnaissance, web vulnerability scanning, API testing, binary analysis, and mobile app analysis through an MCP interface.MIT
- AlicenseBqualityDmaintenanceAn MCP server for authorized bug bounty work that enforces an evidence-driven workflow with session management, preflight checks, surface discovery, and verified scanning.12MIT
- AlicenseCqualityBmaintenanceEnables authorized pentest and bug bounty workflows from any MCP client, with scoped recon, per-host rate limits, and scanner output turned into deduplicated, triaged finding cards.928 PyPI2MIT
- FlicenseNot gradedqualityDmaintenanceWraps multiple bug bounty platform APIs (HackerOne, Bugcrowd, etc.) behind a uniform MCP tool surface, enabling LLM agents to query programs, scope, and briefs across platforms through a single interface.-
- FlicenseAqualityCmaintenanceMCP server providing direct tool-access to security-testing primitives for bug bounty hunting, including recon, request replay, IDOR/BOLA fuzzing, vulnerability detection, secrets scanning, and persistent hunt memory with confidence-scored findings.38-
TDQS
Scored across 33 tools
Most tools have clearly distinct purposes, and descriptions explicitly cross-reference alternatives (e.g. get_report vs get_org_report, add_report_comment vs add_triage_comment). A few pairs like search/search_programs and the various get_program* tools could momentarily confuse, but the descriptions resolve them.
Nearly all names follow a snake_case verb_noun pattern (get_report, list_my_reports, submit_report, update_report_status). Minor deviations like bare 'search' and 'get_taxonomy' are readable but slightly inconsistent.
33 tools is heavy for a single MCP server and falls into the 25+ range, which the rubric marks as too many. Although the bug bounty domain is broad with dual researcher/organisation roles, the surface could reasonably be split into smaller role-specific sets.
The tool surface covers the main researcher and organisation triage workflows well: report lifecycle, comments, grading, appeals, certificates, notifications, profiles, and programme search. Some lifecycle operations (programme management, terms acceptance, payments, disclosure approval) are intentionally delegated to the website, leaving only minor gaps.