Bug Bounty MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_techniquesA | Search the entire bug bounty knowledge base for techniques, payloads, and methodologies. Use this to find information about specific vulnerability types, attack techniques, bypass methods, or security testing approaches. |
| get_payloadsA | Get payloads and attack vectors for a specific vulnerability category. Returns relevant payload lists, bypass techniques, and exploitation methods from PayloadsAllTheThings and HackTricks. |
| read_knowledge_fileA | Read a specific file from the bug bounty knowledge base. Use this after searching to read the full content of a relevant file. |
| browse_knowledge_baseA | Browse the directory structure of the bug bounty knowledge base. Use this to discover what topics and categories are available. |
| get_bounty_reportsA | Get real-world bug bounty reports, both accepted and rejected. Use accepted reports for methodology and impact examples. Use rejected reports to understand what NOT to submit. |
| assess_report_qualityA | Evaluate whether a potential bug bounty finding is likely to be accepted or rejected, based on historical patterns of accepted and rejected reports. Provide vulnerability details to get an assessment. |
| get_methodologyA | Get structured bug bounty testing methodology and checklists. Returns step-by-step approaches for testing specific vulnerability types or general web application testing. |
| get_rs0n_methodologyA | Get rs0n's (Harrison Richardson) battle-tested bug bounty methodology from the DEFCON 32 Bug Bounty Village workshop. This is the PRIMARY methodology that should guide all testing. Covers four pillars: Recon, Injection, Logic, and Cloud. |
| get_cloud_securityB | Get cloud-specific security testing information for AWS, Azure, GCP, and other cloud platforms. |
| get_waf_bypassB | Get WAF (Web Application Firewall) bypass techniques for specific vulnerability types. |
| list_wordlistsA | Browse available SecLists wordlists by category. Returns directory listings of available wordlists for directory brute-forcing, subdomain enumeration, fuzzing, password testing, and more. |
| get_wordlistA | Get the contents of a specific SecLists wordlist file. Use this to retrieve wordlists for directory brute-forcing, fuzzing, subdomain enumeration, or other testing tasks. |
| search_wordlistsA | Search for wordlists across SecLists by filename or keyword. Use this to find the right wordlist for a specific testing task. |
| get_recommended_wordlistB | Get a recommended wordlist for a specific testing task. Returns the best SecLists wordlist based on common bug bounty use cases. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clear, distinct purpose. Methodology tools are differentiated as general vs. specific (rs0n's). Wordlist tools cover recommendation, content retrieval, listing, and searching. Knowledge base tools (browse, read, search) are separate operations. No overlapping responsibilities.
All tools follow a consistent verb_object pattern with snake_case. Predominantly use 'get_' for data retrieval, with other verbs like 'assess', 'browse', 'list', 'read', 'search'. No mixing of conventions.
14 tools is well-scoped for a bug bounty assistance server. It covers methodology, payloads, wordlists, knowledge base access, and report assessment without being overwhelming or too sparse.
The tool set provides comprehensive support for bug bounty testing: methodology (general and specific), payloads, WAF bypass, cloud security, wordlist management, report quality assessment, and real-world reports. There are no obvious missing features.